Closed
Description
as mentioned at https://gist.github.com/zzzeek/dd590d0a3485b7f19cab0322c48ece36. as expanding IN works in all cases now it should be the only IN implementation.
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
No branches or pull requests
Activity
zzzeek commentedon May 12, 2019
this might be doable for 1.4 but need to evaluate:
zzzeek commentedon May 18, 2019
compiler has a flag, "expanding_in=[auto|True|False]". StrSQLCompiler sets it to false. "auto" means if the bindparam inside of in_() has a value, we render as individual params. True is when we invoke for caching.
sqla-tester commentedon Dec 9, 2019
Mike Bayer has proposed a fix for this issue in the master branch:
Use expanding IN for all literal value IN expressions https://gerrit.sqlalchemy.org/1607
Use regex to compare SQL strings with IN
Update git submodules
Create a real type for Tuple() and handle appropriately in compiler
1 remaining item