Yeah my bad, the original query does indeed query for (Z.id, B.name). I had
just changed it to A.name to get the printout for the workaround query
and forgot to change it back before pasting here.
If there's something I can do to contribute (not sure I'm qualified to
write those tests), do
heh :) the thing about tests is that anyone who gets a couple of days of
practice writing them in our style can be very productive...but everyone has
just one issue they need so that threshold isn't passed ...
I have a boatload of tests to write for the 0.7.4 milestone so I'll be blocking
I encountered a little strangeness when joining to a class using single
table inheritance.
I was wondering why I got no results for one particular query.
This was originally encountered with PostgreSQL but was successfully
reproduced with SQLite.
Is this a bug or a user error?
On Nov 15, 2011, at 8:54 PM, Alex Grönholm wrote:
query = session.query(Z, A.name).outerjoin(Z.b).filter(Z.id == 1)
print query
# WORKAROUND:
# query = session.query(Z, A.name).outerjoin(Z.b).filter(Z.id == 1)
# ^- use the superclass instead
I'd note that these
On Nov 15, 2011, at 11:39 PM, Michael Bayer wrote:
On Nov 15, 2011, at 8:54 PM, Alex Grönholm wrote:
query = session.query(Z, A.name).outerjoin(Z.b).filter(Z.id == 1)
print query
# WORKAROUND:
# query = session.query(Z, A.name).outerjoin(Z.b).filter(Z.id == 1)
#
