[sqlalchemy] Re: unexpected behaviour of in_

2008-06-13 Thread Egil Möller
You seem to have stumbled into the same bug as I have while i fixed the IN SQL generation code for oracle to work inside the column list, not just in the where-clause. I ended up hacking SQLAlchemy/trunk/lib/sqlalchemy/sql/expression.py like this: 2166

[sqlalchemy] Re: unexpected behaviour of in_

2008-06-12 Thread Michael Bayer
this is ticket #1074. A slightly klunky workaround for now is: col = t1.c.c1.in_([select([t1.c.c1]).as_scalar()]) On Jun 12, 2008, at 10:04 AM, casbon wrote: Hi All, I am seeing something I didn't expect using in_. Here is a simple example, exactly as I expect: In [13]: col =

[sqlalchemy] Re: unexpected behaviour of in_

2008-06-12 Thread casbon
Ah, thanks. Should have searched the bug reports as well as the list. On Jun 12, 3:27 pm, Michael Bayer [EMAIL PROTECTED] wrote: this is ticket #1074.   A slightly klunky workaround for now is: col = t1.c.c1.in_([select([t1.c.c1]).as_scalar()]) On Jun 12, 2008, at 10:04 AM, casbon wrote:

[sqlalchemy] Re: unexpected behaviour of in_

2008-06-12 Thread Michael Bayer
On Jun 12, 2008, at 10:51 AM, casbon wrote: Ah, thanks. Should have searched the bug reports as well as the list. no no, I just created that ticket :) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups