Supabase Wrappers: A framework for building Postgres foreign data wrappers

Post by kiwicopple » Fri, Dec 16, 2022, 8:37 AM UTC

atonse wrote: post #37

kiwicopple wrote: post #6

Earlier quoted context omitted.

> speaks a particular API over the network it's a interesting idea, and one of the things that we were toying with in our pg_net extension ( https://github.com/supabase/pg_net ). This is a "generic" async network extension, so you can fetch/put/post. It works well for APIs. I think the generic approach works for some things where the data is less "fixed" - for example, an OpenAI API endpoint. But for "fixed" data (da…

I don't think so... in your example those are functions we just call in SQL right? I'm talking about exposing arbitrary data as a table like an FDW, but without having to compile a whole module. So more like, (this is a bit contrived but bear with me): Let's say I wanted to make a table that lists all my keybase proofs (so sad Keybase is basically dead, but I digress). I'd build a graphql endpoint where you can query…

    create server example_api
      foreign data wrapper example_api_wrapper
      options (
        open_api_url 'https://api.example.com/'
      );

    GET -> SELECT (which would map selected columns into a table)
    POST -> INSERT
    PATCH -> UPDATE
    DELETE -> DELETE

Post by intrasight » Fri, Dec 16, 2022, 2:21 PM UTC

radiowave wrote: post #13

jzelinskie wrote: post #8

I really want to love foreign data wrappers for Postgres and this seems like a big improvement over existing Python library, but the lack of support for them in managed databases services makes them a non-starter for so many use-cases. Because RDS, for example, will only support the foreign data wrapper for reading from another "Postgres", what we really need is a server that supports the Postgres wire protocol (easi…

Never tried this with RDS, but it's entirely possible to use postgres_fdw to interact with a foreign table on another postgres server, where you might have more choice about what extensions you run. I'm doing this right now because I have a postgres installation that it's not yet convenient to upgrade beyond v12, but where I'd really like the benefit of the recently-improved JDBC FDW, which requires at least v13.

Post by chrisjc » Fri, Dec 16, 2022, 3:05 PM UTC

burmecia wrote: post #39

chrisjc wrote: post #33

Earlier quoted context omitted.

The blog post, repo and your comment still leave me a little confused about what Supabase's wrappers project is, the intent and its current state. So this "wrappers" project is just a framework that simplifies the development and manages the curation and distribution of Postgres Foreign Data Wrappers? At the end of the day, are these just FDWs that run on top of any Postgres instance? Do I have to run Supabase to tak…

| At the end of the day, are these just FDWs that run on top of any Postgres instance? Yes, the FDWs developed by Wrappers can be used on any Postgres db. | Do I have to run Supabase to take advantage of the FDWs created through this framework? No, you don't need to. Those are just normal FDWs can be used on any Postgres db. | Is there a generic JDBC/SQL/etc FDW for any SQL based database like Snowflake, Oracle, etc?…