quick easy fix is to use result set mapping instead, or feed a full
select() statement into query.select(), which will skip the whole
compilation step.
i would like a small test case attached for this one so i can play
with it, though. for example i dont see why its deciding to use the
nesting
Sorry if this posts twice... I didn't get a Message has been sent
page last time..
I posted a bug with a test case here:
http://www.sqlalchemy.org/trac/ticket/449
Thanks
Dennis
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
I've created a bug with an attached test:
http://www.sqlalchemy.org/trac/ticket/449
Thanks!
-Dennis
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
Just a quick note, I tried out your suggestion to pass in a select
statement.
That does indeed work. There is an issue though, I tried using the
contains_eager('myproperty') as noted in the docs and that only worked
in combination with eagerload('myproperty'). I think the reason is
that in the
On Jan 31, 4:57 pm, Dennis [EMAIL PROTECTED] wrote:
little confusing, but perhaps it is supposed to be that way. I would
have thought that contains_eager implies eagerload.
great idea. i threw that into rev 2284.
--~--~-~--~~~---~--~~
You received this
