Michael Bayer wrote:
You need to set allow_null_pks=true on your mapper. This will be on
by default in 06.
I am running into the same problem, but I use declarative.
After some search and looking at mapper.py I figured out I could do this:
db.Vcbook.__mapper__.allow_null_pks = True
On May 3, 2009, at 5:14 AM, Werner F. Bruhin wrote:
Michael Bayer wrote:
You need to set allow_null_pks=true on your mapper. This will be on
by default in 06.
I am running into the same problem, but I use declarative.
After some search and looking at mapper.py I figured out I could do
Thanks. I do appreciate that this will become the default as I think
that if you ask for an outer join that's what you expect.
thanks again for you time
sandro
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Missing an answer I opened ticket #1392:
http://www.sqlalchemy.org/trac/ticket/1392#preview
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
You need to set allow_null_pks=true on your mapper. This will be on
by default in 06.
On Apr 27, 2009, at 3:40 AM, sandro dentella san...@e-den.it wrote:
Missing an answer I opened ticket #1392:
http://www.sqlalchemy.org/trac/ticket/1392#preview
Hi,
Mike, should I file a ticket for this?... or I just misinterpreted
the result?
sandro
*:-)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
Adding this to the test shows that the generated sql does retrieve 3 rows as
expected.
for r in sess.execute(q):
print r
I suspect it has something to do with the identity mapping. Maybe someone
who understands that could help with an explanation. Knowing my data, I
could have a similar
