Re: [sqlalchemy] Problems with retroactive changes to Query objects

2013-01-30 Thread Hans Meine
Hi Michael! Am Dienstag, 29. Januar 2013, 12:23:01 schrieb Michael Bayer: … it's usually going to complicate things if you mix implicit and explicit joins together. The issue should be solved if you create a clean string of joins: s.query(results1.id,

Re: [sqlalchemy] Problems with retroactive changes to Query objects

2013-01-30 Thread Michael Bayer
On Jan 30, 2013, at 8:47 AM, Hans Meine wrote: I am still not sure if this confusion isn't a bug or weakness in SA that should be either fixed or handled with a more explicit error message. the usage pattern as is will likely never be feasible; SELECT * FROM A, B JOIN C on onclause, and