Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BigQuery wrapper: all columns must be defined #69

Closed
yan-hic opened this issue Mar 10, 2023 · 1 comment · Fixed by #74
Closed

BigQuery wrapper: all columns must be defined #69

yan-hic opened this issue Mar 10, 2023 · 1 comment · Fixed by #74
Labels
documentation Improvements or additions to documentation

Comments

@yan-hic
Copy link

yan-hic commented Mar 10, 2023

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.

@yan-hic yan-hic added the documentation Improvements or additions to documentation label Mar 10, 2023
@yan-hic
Copy link
Author

yan-hic commented Mar 11, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant