hi
all my tests run ok on this (as well 0.4), except the concrete-inh
case reported in
http://groups.google.com/group/sqlalchemy/browse_thread/thread/92417a6f215fa8d8/c72eb562a3070bd9
- attached again.
it's about concrete inh B of A, where polymunion contains only B, and
there are instances of
one thing that might go in a wishlist - query.filter_or()
http://groups.google.com/group/sqlalchemy/browse_thread/thread/f6798eb5ef2c0bfe
should i make it into a ticket?
as you might have noticed we've merged 0.5 into the trunk.
--~--~-~--~~~---~--~~
You
what does q.filter(x==5).filter_or(x==9).filter(y=17).filter_or(x==27)
do ? (x=5 or x=9) and (y=17 or x=27) ? ((x=5 or x=9) and y=17) or
x=27 ? etc ..
On May 12, 2008, at 8:06 AM, [EMAIL PROTECTED] wrote:
one thing that might go in a wishlist - query.filter_or()
On Monday 12 May 2008 17:01:23 Michael Bayer wrote:
what does
q.filter(x==5).filter_or(x==9).filter(y=17).filter_or(x==27) do ?
(x=5 or x=9) and (y=17 or x=27) ? ((x=5 or x=9) and y=17) or x=27
? etc ..
what pythons/C x==5 or x==9 and y==17 or x==27 does?
i know... the parenthesises.
-1.
It's confusing, and there's already an extant or_ function that's documented
and not confusing. The proposal is no more cooked than it was five months
ago.
On Mon, May 12, 2008 at 11:58 AM, [EMAIL PROTECTED] wrote:
On Monday 12 May 2008 17:01:23 Michael Bayer wrote:
what does
I dont see how this:
cls.query.left_bracket().filter_or(cls.y ==
17).filter_or(cls.x==27).right_bracket()
is clearer than this:
cls.query.filter(or_(cls.y == 17, cls.x==27))
Also, another vote for cutting off python 2.3. Seriously, it's 2008.
On Mon, May 12, 2008 at 11:58 AM, [EMAIL PROTECTED]
On May 12, 2008, at 11:58 AM, [EMAIL PROTECTED] wrote:
On Monday 12 May 2008 17:01:23 Michael Bayer wrote:
what does
q.filter(x==5).filter_or(x==9).filter(y=17).filter_or(x==27) do ?
(x=5 or x=9) and (y=17 or x=27) ? ((x=5 or x=9) and y=17) or x=27
? etc ..
what pythons/C x==5 or x==9
On Monday 12 May 2008 18:12:39 Bobby Impollonia wrote:
I dont see how this:
cls.query.left_bracket().filter_or(cls.y ==
17).filter_or(cls.x==27).right_bracket()
is clearer than this:
cls.query.filter(or_(cls.y == 17, cls.x==27))
it's not. it's not about replacing the or_. noone should use it
cls.query.left_bracket().filter_or(cls.y ==
17).filter_or(cls.x==27).right_bracket()
is clearer than this:
cls.query.filter(or_(cls.y == 17, cls.x==27))
it's not. it's not about replacing the or_. noone should use it
that way...
u have horses and owners with houses and hats.
On May 12, 2008, at 1:48 PM, [EMAIL PROTECTED] wrote:
cls.query.left_bracket().filter_or(cls.y ==
17).filter_or(cls.x==27).right_bracket()
is clearer than this:
cls.query.filter(or_(cls.y == 17, cls.x==27))
it's not. it's not about replacing the or_. noone should use it
that way...
u
Is the stuff from user_defined_state branch merge in ?
If so is the __sa_instrument_class__ stuff the same ?
Michael Bayer wrote:
hey list -
as you might have noticed we've merged 0.5 into the trunk. this
version is already spectacular and I encourage everyone to start
poking
Trunk Rev 4726
Note the following:
Python 2.5.2 (r252:60911, May 7 2008, 15:19:09)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type help, copyright, credits or license for more information.
from sqlalchemy import *
Traceback (most recent call last):
File stdin, line 1, in module
File
Steve Zatz wrote:
Trunk Rev 4726
Note the following:
Python 2.5.2 (r252:60911, May 7 2008, 15:19:09)
[GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2
Type help, copyright, credits or license for more information.
from sqlalchemy import *
Traceback (most recent call last):
File stdin,
be sure to clean out the .pyc files.
That worked. Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this
14 matches
Mail list logo
