-
Notifications
You must be signed in to change notification settings - Fork 846
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
Support CrateDB #336
Support CrateDB #336
Conversation
Thanks! Looks like as clean and narrow a change as we could hope for. |
Thanks a lot! I'll be around to help if anybody runs into any unexpected issues with this. |
Nice to see CrateDB support in pgx. One question to the It would be fairly simple for us to add the The reason I'm asking is that this way we could add |
@mfussenegger not sure about @jackc, but from my POV changing the query to explicitly target the pg_catalog schema should be a reasonable change. As far as I can tell the pg_catalog schema has been around and can be explicitly specified in queries since at least Postgres 7.3. That being said, I think the workaround code should probably still need to stay in place to support older CrateDB versions for a while. |
No objections from me for explicitly qualifying the |
@mfussenegger let me know when |
See https://www.postgresql.org/docs/10/static/catalog-pg-type.html For now all types default to `b` (base type). `pgx` is one client that uses this column. See jackc/pgx#336
@felixge We've added the column (see crate/crate#6582) - will be part of 2.3 (or in the nightly builds starting tomorrow) |
@mfussenegger cool. I'm traveling for the next three weeks, but I'll try to find some time to make a PR for this ASAP. |
See #320
@jackc I spend a decent amount of time trying to come up with a minimally invasive patch and added some detailed in-line comments explaining my approach. Let me know what you think.