-
Notifications
You must be signed in to change notification settings - Fork 17
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
Allow inserttable() to take columns as parameter #24
Comments
Actually I don't think a (copied from Trac 2019-04-25) |
Justin: I don't think we're talking about the same thing. The request was to allow inserting columns "a,c" into a table with columns "a,b,c,d" (we need to do this all the time). That's needed in case columns b,d have default values (otherwise NULL would work fine). Doesn't this just need to accept an optional list of column names and join them with commas? I don't know for sure if we'd be able to use this for either of our loaders, but I suspect it would be competitive or better than prepared statements, for use cases where it can be applied. (copied from Trac 2019-05-14) |
See discussion on the mailing list 2020-06-20, will be released in 5.2. |
Suggested on the mailing list 2017-01:
The method
Connection.inserttable(table, values)
in the classic module might take more parameters, e.g.columns
, similar to theCursor.copy_from(...)
method in the DB API 2 module.(copied from Trac ticket 73, created 2018-04-23)
The text was updated successfully, but these errors were encountered: