Re: [sqlalchemy] Possible bug in select.append_whereclause()?

2013-08-29 Thread Michael Bayer
On Aug 28, 2013, at 11:48 PM, gbr doubl...@directbox.com wrote: to compile the WHERE clause of query means we look at query.c.id which means we must render the table query which is how it cycles. Why does it need to compile the whole query when I just want to use than column name of

Re: [sqlalchemy] Possible bug in select.append_whereclause()?

2013-08-29 Thread gbr
I see. I probably have to go back to the drawing board and revise how the whole thing works. Thanks anyway for the insight. At least I know that there isn't much I can do this way (the query actually consists of many joins). Handy to know how to access the from clause (unrelated to my post,

[sqlalchemy] Possible bug in select.append_whereclause()?

2013-08-28 Thread gbr
Hi, Before spamming the issue tracker and since I'm new to SQLAlchemy and may have misunderstood how to use `append_whereclause()`, I thought I seek confirmation on this mailing list. The code: def test_append_whereclause(self): url = 'localhost' username = 'donald'

Re: [sqlalchemy] Possible bug in select.append_whereclause()?

2013-08-28 Thread Michael Bayer
On Aug 28, 2013, at 10:11 PM, gbr doubl...@directbox.com wrote: Hi, Before spamming the issue tracker and since I'm new to SQLAlchemy and may have misunderstood how to use `append_whereclause()`, I thought I seek confirmation on this mailing list. The code: def

Re: [sqlalchemy] Possible bug in select.append_whereclause()?

2013-08-28 Thread gbr
to compile the WHERE clause of query means we look at query.c.id which means we must render the table query which is how it cycles. Why does it need to compile the whole query when I just want to use than column name of the query? What it seems like you're looking to do is