wrappers

GitHub repo is here if you want to use this for self-hosted Postgres databases: https://github.com/supabase/wrappers

Agree, Rust and Postgres and a perfect match. It feels so much more productive to write Postgres tooling in Rust. E.g. we already have extensions like pg_graphql[0], pg_jsonschema[1] and wrappers[2] which use pgrx. We don't have plrust on the platform yet though. Full disclosure: I'm a Rust Engieer at Supabase. [0] https://github.com/supabase/pg_graphql [1] https://github.com/supabase/pg_jsonschema [2] https://github.com/supabase/wrappers

I used one of their open source work in a project: https://github.com/supabase/wrappers It’s appreciated since SaaS on AWS wasn’t a possibility.

I’m currently playing with PostgreSQL, foreign data wrappers, and pgrx rust extensions. My development experience has been surprisingly smooth and enjoyable. My main issue is that joins will be processed locally, so all the foreign data will be fetched before the join happens. But otherwise basic CRUD is easy. https://wiki.postgresql.org/wiki/Foreign_data_wrappers https://github.com/pgcentralfoundation/pgrx https://github.com/supabase/wrappers

> On a sidenote, is not the wrappers for Airtable, BigQuery and ClickHouse opensourced? Or why did they skip that column in the second table? All of the wrappers are open source. You can see the source for the Airtable, BigQuery, and ClickHouse wrappers here https://github.com/supabase/wrappers/tree/5fac8afb62e6e8362b... The `self-hosted` column is only missing from the "under development" wrappers in the blog post's table because those are not production ready and shouldn't be self hosted (yet). > Is all of supabase opensourced now? Yep! The whole stack is open source and can be self hosted

> How do you mock it? How do you test it? Stripe and Firebase both offer test endpoints for their services. The foreign data wrappers for each allow subbing in a user defined endpoint in their `options` so thats how I'd recommend testing the two that have released. Some of the pre-release integrations can be spun up locally in docker e.g. clickhouse. The FDWs for those similarly take an arbitrary connection string making it pretty straightforward to write tests. Here's an example from the repo https://github.com/supabase/wrappers/blob/5fac8afb62e6e8362b... > Add custom logic? Views! > tasks that the database is not designed to do The C API for foreign data wrappers is baked right into Postgres proper. They've been around since 2013 and are pretty battle hardened at this point. Supabase Wrappers exposes that API in rust so users can write

You'd need to build a specific wrapper for that API. For example, here[0] is the wrapper for Stripe (docs[1]) I think you're looking for something more generic, like pg_net[2]. This would allow you to do your crazy logic by parsing your API response: select net.http_get('https://news.ycombinator.com') as request_id; select body, status_code from net.http_collect_response(1, async:=false); [0] Stripe src: https://github.com/supabase/wrappers/tree/main/wrappers/src/... [1] Stripe docs: https://supabase.github.io/wrappers/stripe/ [2] pg_net: https://supabase.github.io/pg_net/api/

hey hn, supabase ceo here this one might be more in of a “Show HN” because it’s a pre-release - something that you might want to try yourself or contribute to. The GitHub repo is here: https://github.com/supabase/wrappers For context, Postgres has Foreign Data Wrappers (FDW) [0]. These allow you to connect one Postgres database to another, and then query the secondary database directly in the first. CREATE FOREIGN TABLE other_database_table ( id integer, title text ) SERVER other_database; The data does not need to be “moved” to the primary database - it stays in the secondary and is fetched when you run a select query: select * from other_database_table; Our release today is a framework which extends this functionality to other databases/systems. If you’re familiar with Multicorn[1] or Steampipe[2], then