-
Notifications
You must be signed in to change notification settings - Fork 408
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
Can't resolve tuple argument types #476
Comments
I haven't seen there any support of tuple unpacking. I'd separate parameters to |
Unfortunately, I can't do it - I'm using |
This is a PostgreSQL protocol limitation. Anonymous row types (tuples) cannot be described. The error handling in this case could be better, sure. @LEW21 If you can afford it, I would suggest declaring an explicit composite type:
and then
|
Currently asyncpg would crash with an arcane "could not resolve query result and/or argument types in 6 attempts", which isn't helpful. Do the right thing by raising an `UnsupportedClientFeatureError` explicitly instead. Fixes #476.
Currently asyncpg would crash with an arcane "could not resolve query result and/or argument types in 6 attempts", which isn't helpful. Do the right thing by raising an `UnsupportedClientFeatureError` explicitly instead. Fixes #476.
the issue with a local PostgreSQL install?: No, it's on docker
uvloop?: Didn't try uvloop.
asyncpg is unable to resolve argument types for the following SQL query:
Complete example - this script fails:
with
The text was updated successfully, but these errors were encountered: