Supabase’s Post

I just published an update to the dremio-simple-query library on Pypi, making it super easy to connect and query your Dremio instance using Apache Arrow. Dremio becomes super easy access in any notebook anywhere! https://lnkd.in/eX5PiV9q Updates Include: - added a toPandas and toPolars functions that'll return the results of your query in the dataframe library of your choice, this is in addition to the existing toArrow and toDuckDB methods - added a get_token function to get a Dremio PAT token using Dremio's rest API making getting everything setup for Dremio software easier in particular. - Added detail on getting your Dremio Arrow URI in the documentation

📣 I am happy to share my new Medium article, End-To-End Data Flow Project. In this project, I transferred live-stream exchange rates from API via Apache NiFi to Slack Application and SQL table with DBeaver. Please click the Medium link below to reach the whole steps. #datascience #dataengineering #datascientist #apachenifi #dataflow

As a part of task given by Code Alpha , I designed a survey form .In this one can submit the data somewhere, whether via email or stored in a database. GitHub Repository :https://lnkd.in/drD7Ab7f #codealpha #webdevelopment

Interested in on-the-fly geospatial conversion tools but don't want to rely on a random website or a GUI ? Try xyzeus's suite of nearly 100 conversion functions. Supported conversion formats in include geojson, shapefile, KML, WKT, H3, geoparquet, geodataframe, geohash, GPX, GeoPackage, topojson, postgreSQL, SQLite, DXF and many more ! A few geojson conversion methods have been listed below...

#RFC Alert: Proposing an inverted index for tag columns in the #MitoEngine to boost filtering and performance alongside the Primary Keys' Min-Max index. Dive deeper：https://lnkd.in/gmzXpfK2 #opensource #database #PerformanceEnhancement

Dev update June 2024 ⚒️ We have multiple updates and new features to share with you this month. Let's dive in! https://lnkd.in/dfZ8nDrg - Edge Runtime Inspector Feature (CLI) 🔍 We’ve introduced the Edge Runtime Inspector, a powerful new feature in the CLI that helps you inspect and debug edge functions more efficiently. https://lnkd.in/dxkn3atD - View and Abort Running Queries (Supabase Studio) 👀 You can now view and abort queries currently running on your database (primary or replica) in the Supabase Studio SQL Editor. This feature gives you greater control and flexibility in managing your queries https://lnkd.in/dNnDqYjG - Logging Integration With The ELK Stack 📄 The Logflare to Elastic filebeat backend has been merged. This integration enables log drains to ELK stacks, providing more robust logging and monitoring capabilities - Interpreting Supabase Grafana I/O Charts 📊 We have published a guide on how to use the Supabase I/O charts to identify when you may need to scale your database, optimize your queries, or spin up a read replica https://lnkd.in/dSyhXFFu - New Engineering and Troubleshooting Guides ⚒️ How Postgres chooses which index to use Using SQLAlchemy with Supabase Supabase & Your Network: IPv4 and IPv6 compatibility Understanding the Usage Summary on the Dashboard Supavisor and Connection Terminology Explained Prisma Error Management How to change max database connections Inspecting edge function environment variables And much, much more. Read here: https://lnkd.in/dfZ8nDrg

I ran a demo for a prospect the other day using their provided spatial SQL logic. It required a self join between all 12.7 ish million parcel polygons in California based on distance (ST_DWITHIN). Running with Apache Sedona in Wherobots and writing out the results ran in under 10 seconds (medium sized instance). I got curious how long this would take on all 157m parcel polygons… same query, same distance based self join… completed in 63 seconds. No -99999 error, no unresponsive toolbox window… It. Just. Worked.

Here are 3 types of scan you didnt know about in postgres Sequential Scan Index Scan & Bitmap Heap Scan Use the EXPLAIN or EXPLAIN ANALYZE infront of your Query Outputs the type of scan, the planning time and the execution time

Here are 3 types of scan you didnt know about in postgres Sequential Scan Index Scan & Bitmap Heap Scan Use the EXPLAIN or EXPLAIN ANALYZE infront of your Query Outputs the type of scan, the planning time and the execution time

https://lnkd.in/dFzuUY3x << ...Ingestr is a command-line application that allows you to ingest data from any source into any destination using simple command-line flags, no code necessary... >>