this needed an adjustment to the EagerLoader's determination of what
table it should attach its outerjoin onto, which you can see in
changeset 1907 (and some more in 1909). I converted the test program
into a new unittest suite for eagerloading which is in rev 1908, and
also added a test that uses SelectResults, which seems to produce the
identical SQL to that of the "from_obj" version. the SelectResults
looks really nice:
q=SelectResults(s.query(Test).options(eagerload('category')))
l=q.select (
and_(tests.c.owner_id==1,or_
(options.c.someoption==None,options.c.someoption==False))
).outerjoin_to('owner_option')
the test can be run from the distro directory for any kind of database:
python test/orm/eagertest3.py --verbose --log-info=sqlalchemy.engine
--dburl "postgres://scott:tiger@/test"
On Sep 27, 2006, at 1:31 PM, Dennis Muhlestein wrote:
> On 9/27/06, Michael Bayer <[EMAIL PROTECTED]> wrote:
>> it would be a big favor if you could create a little standalone
>> program illustrating the various cases for me.
>
> I've attached a case showing the problem. I ran this against the
> latest (1904)
>
> Thanks
> Dennis
> <reltest.py>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
