[web2py] Left Join with aliased table and the new DAL

2010-12-21 Thread HaM
Hi everyone, I currently use Web2py for an internal corporation application. I recently upgraded from 1.89 to 1.90-6. Since this upgrade all my left joins with aliased table don't work any more. I'm using Web2py with Postgres. For example I have this in a controller exposed function: Doma

[web2py] Re: Left Join with aliased table and the new DAL

2010-12-21 Thread HaM
I just tried with the last revision (1414:da25156addab) and the problem stills the same.

[web2py] Re: Left Join with aliased table and the new DAL

2010-12-22 Thread HaM
  Manager.on(Manager.id==Client.manager_id)]) > print sql > > what do you get? > I get > > SELECT  domain.id, domain.name, domain.client_id, client.id, > client.name, client.manager_id, manager.id, manager.name FROM domain > LEFT JOIN client ON (client.id = domain.client_id) LEFT J

[web2py] Re: Left Join with aliased table and the new DAL

2010-12-27 Thread HaM
fixed. The second > problem is not a new dal issue. It is just that aliased tables in > INNER JOINs never worked well. I will continue to look into it. This > may take a while so could you open a ticket on google code? Thanks. > > On Dec 22, 2:52 am, HaM wrote: > > > Ok in o

[web2py] INNER JOIIN and aliased table

2010-12-27 Thread HaM
Hi, I'm trying to do INNER JOIN with aliased table and I'm experiencing problem. Here is my example: Domain = db.domain Client = db.client Manager = db.contact.with_alias('manager') sql = db((Domain.id==1)& (Client.id==Domain.client_id)& (Manager.id==Client.manager_id))._select(

[web2py] Re: INNER JOIIN and aliased table

2010-12-28 Thread HaM
No :) On Dec 27, 6:03 pm, mdipierro wrote: > Did this work with the old dal? > > On Dec 27, 9:41 am, HaM wrote: > > > Hi, > > > I'm trying to do INNER JOIN with aliased table and I'm experiencing > > problem. > > Here is my example: > >

[web2py] Re: Left Join with aliased table and the new DAL

2010-12-28 Thread HaM
It's fixed for me. It works with revision 1454:c4465e21c715 Thanks ! On Dec 27, 8:11 pm, mdipierro wrote: > This should now be fixed in trunk. Please confirm. > > On Dec 27, 3:23 am, HaM wrote: > > > First, Merry Christmas. > > > Since I still experiencing pr