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

Support for Postgres.js with fetch_types: true #3607

Open
refset opened this issue Aug 16, 2024 · 3 comments
Open

Support for Postgres.js with fetch_types: true #3607

refset opened this issue Aug 16, 2024 · 3 comments

Comments

@refset
Copy link
Contributor

refset commented Aug 16, 2024

Currently fetch_types: false is needed

@egg-juxt
Copy link
Contributor

Related #3582

@jarohen
Copy link
Member

jarohen commented Aug 28, 2024

@refset mind fleshing this out with why (if indeed we know)?

@egg-juxt
Copy link
Contributor

egg-juxt commented Aug 28, 2024

PostgresJS fetches the oids of array types at the first connection, in order to install type parsers/serializers for those array types. We don't currently have array types in our pg_catalog.pg_type table, so this wouldn't actually do anything. We also don't support some of the columns in the query (see #3582). So in practice we could just document the use of fetch_types: false.

However, I think it's important to clarify why that initial query fails with a 'malformed-query' error. The query should actually work I think and return no rows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants