You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The BQ wrapper works great out-of-the-box on supabase cloud. A game changer really for us as we only started evaluating SB yesterday.
One word of caution though - or a feature request ?: when creating the PG foreign table as per the instructions, the list of columns must match exactly the source table. Ideally one would want to define any subset instead i.e. if you only need the read a few fields. If no plan to change, please update the documentation ( + also update https://supabase.com/docs/guides/database/extensions/wrappers and https://supabase.github.io/wrappers/ as BigQuery is available)
Workaround (especially if lots of columns): create & use a BQ view as source.
The text was updated successfully, but these errors were encountered:
By extension, this leads to an enhancement request namely allowing a query in the server table option as seen in others fdws like laurenz/oracle_fdw@b96f9d9
The BQ wrapper works great out-of-the-box on supabase cloud. A game changer really for us as we only started evaluating SB yesterday.
One word of caution though - or a feature request ?: when creating the PG foreign table as per the instructions, the list of columns must match exactly the source table. Ideally one would want to define any subset instead i.e. if you only need the read a few fields. If no plan to change, please update the documentation ( + also update https://supabase.com/docs/guides/database/extensions/wrappers and https://supabase.github.io/wrappers/ as BigQuery is available)
Workaround (especially if lots of columns): create & use a BQ view as source.
The text was updated successfully, but these errors were encountered: