Re: [sqlalchemy] Is there a reason why there is no dialect specific fix for ORA-01795?

On 6/17/14, 9:30 AM, Ofir Herzas wrote: > This can be done only for Oracle and only if the number of expressions > is higher than 1000 (which would otherwise produce an exception) > Regarding complex queries, I guess the several or_'s fix should work: > or_(x.in_(1...1000), x.in_(1001...2000)) > >

Re: [sqlalchemy] Is there a reason why there is no dialect specific fix for ORA-01795?

This can be done only for Oracle and only if the number of expressions is higher than 1000 (which would otherwise produce an exception) Regarding complex queries, I guess the several or_'s fix should work: or_(x.in_(1...1000), x.in_(1001...2000)) How can this be done locally? (override in_ opera

Re: [sqlalchemy] Is there a reason why there is no dialect specific fix for ORA-01795?

On 6/17/14, 4:32 AM, Ofir Herzas wrote: > ORA-01795: maximum number of expressions in a list is 1000 > > As I understand, there are several options to fix this issue > (e.g. > https://groups.google.com/forum/#!searchin/sqlalchemy/maximum$20number$20of$20expressions/sqlalchemy/Oa6YWNE0-IQ/6GVmy27B-

[sqlalchemy] Is there a reason why there is no dialect specific fix for ORA-01795?

ORA-01795: maximum number of expressions in a list is 1000 As I understand, there are several options to fix this issue (e.g. https://groups.google.com/forum/#!searchin/sqlalchemy/maximum$20number$20of$20expressions/sqlalchemy/Oa6YWNE0-IQ/6GVmy27B-FAJ or split in_ to several or_) Why not incor