-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
mysql.dml.Insert.values
shadows the generative function sql.expression.Insert.values
#4072
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
Comments
Michael Bayer (@zzzeek) wrote: doh. clearly it has to be some totally different name. |
Michael Bayer (@zzzeek) wrote: anyway nice catch! https://gerrit.sqlalchemy.org/510 it's called .inserted now. |
Michael Bayer (@zzzeek) wrote: Rename MySQL dml.insert().values to .inserted Changed the name of the Change-Id: I8da8e30a3077698385a4b77e2c2032e2d1ff10b2 → 70be731 |
Changes by Michael Bayer (@zzzeek):
|
Michael Bayer (@zzzeek) wrote: thanks, we dodged a bullet on that one. whenever i see a bug report from you I know im going to have to fix something for real... :) |
Jack Zhou (@univerio) wrote: Happy to help. And thank you for the quick fix as always! |
Migrated issue, originally created by Jack Zhou (@univerio)
When using the
ON DUPLICATE KEY UPDATE
support for MySQL, the.values()
generative function is not available, contrary to the claims made by the documentation.It appears to be shadowed by the
.values
property intended to support theVALUES(...)
construct. Perhaps the column collection could be namedvalues_
instead?The workaround is to specify
values
with theinsert
constructor:The text was updated successfully, but these errors were encountered: