-
Notifications
You must be signed in to change notification settings - Fork 105
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
python/postgres: no binary output function available for type aclitem #2567
Comments
That's rather annoying. Hmm. |
Yeah, I found it too. |
For the fetching, is the Arrow support important or would just plain ol' psycopg work? |
Ideally, I would prefer to retrieve the results as an Arrow table. However, I am open to alternative solutions. The core challenge I face is that I need to execute a query within a temporary context immediately after creating tables and schemas, followed by a rollback to the original state. Essentially, I'm building an ephemeral execution context specifically for the input query. |
Ah, so they really do need to be a single driver/connection. |
yes, unfortunately I have no other options |
Unfortunately there's not a way to "turn off" the binary support since the only support is the binary support (we never built a text format parser!) So the only way to support this would be to build a separate set of text format parsers from scratch. |
Could we do a "text only" version where the output schema is always |
What happened?
With the latest version of the library (1.4.0) this query:
fails with:
I can't control the input SQL query, but I could "disable", if it's possible, the binary mode for all the queries against the
pg_catalog
namespace, but it isn't supported.Stack Trace
How can we reproduce the bug?
Environment/Setup
Postgresql 15.5
Python 3.12.3
adbc-driver-postgresql 1.4.0
pyarrow 19.0.1
The text was updated successfully, but these errors were encountered: