You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, I expect, because I am also passing a sqlalchemy connectable, that pg_copy_from would respect the properties of a text object passed as the query (including using the default values of any bound parameters at execution), but it silently converts the text object to a plain str.
A couple of solutions are possible:
Document that the copy extensions convert things to string (and maybe give a warning when getting something other than a string)
Support text objects in a way compatible with user expectations of sqlalchemy
2 seems nicer but 🤷
The text was updated successfully, but these errors were encountered:
As a user, I expect, because I am also passing a sqlalchemy connectable, that
pg_copy_from
would respect the properties of atext
object passed as the query (including using the default values of any bound parameters at execution), but it silently converts thetext
object to a plainstr
.A couple of solutions are possible:
2 seems nicer but 🤷
The text was updated successfully, but these errors were encountered: