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
Expanding bindparam not running bind processors #4198
Comments
Michael Bayer (@zzzeek) wrote: bind param processing logic entirely non functional. wrote the code to process parameters, can take it right out and all the tests pass. here's generalized test:
|
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
Michael Bayer (@zzzeek) wrote: and there you have it
|
Michael Bayer (@zzzeek) wrote: |
Michael Bayer (@zzzeek) wrote: Allow bind processors to work with expanding IN Fixed bug in new "expanding IN parameter" feature where the bind parameter Change-Id: I8e2420d7229a3e253e43b5227ebb98f9fe0bd14a → d746ea9 |
Changes by Michael Bayer (@zzzeek):
|
Migrated issue, originally created by Robert Ditthardt
I'm assuming there are just missing features here because experimental. That said...
Attached is a test file that demonstrates the observed behavior.
I think that it should be unnecessary to need to get the "name" attribute of an enumeration for "in_" queries that require bound parameters that are enumerations. It should be sufficient to just pass in the enumeration as it is when the Table is properly configured.
I should also note that the mysql driver has slightly different behavior. It doesn't throw an exception, but instead just silently generates a bad query, where each enum in the raw sql ends up as "TestEnum.FOO" instead of "FOO".
Attachments: test-sqlalchemy.py
The text was updated successfully, but these errors were encountered: