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 problem on left join I have looked mor
This should now be fixed in trunk. Please confirm.
On Dec 27, 3:23 am, HaM wrote:
> First, Merry Christmas.
>
> Since I still experiencing problem on left join I have looked more
> deeply and try to find where is the difference between old and new
> DAL.
> I found that my problem only appears on
We'll fix this. Pleas open a ticket on google code. Thanks for
bringing this up.
Massimo
On Dec 27, 3:23 am, HaM wrote:
> First, Merry Christmas.
>
> Since I still experiencing problem on left join I have looked more
> deeply and try to find where is the difference between old and new
> DAL.
> I
First, Merry Christmas.
Since I still experiencing problem on left join I have looked more
deeply and try to find where is the difference between old and new
DAL.
I found that my problem only appears on a more complex request:
Domain = dbPsnol.domain
Client = dbPsnol.client
Contact = dbPsnol.cont
I took a second look. The first problem is indeed 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 wr
Ok in order to simplify the problem I have changed my code to this:
Domain = db.domain
Client = db.client
Manager = db.contact.with_alias('manager')
sql = db((Domain.id==1)&(Client.id==Domain.client_id))._select(
Domain.name, Client.name, Manager.name,
left=[Manager
hmm...
I am trying your select and it now generates the same sql as the old
dal. please try this:
Domain = db.domain
Client = db.client
Manager = db.contact.with_alias('manager')
sql = db(Domain.id==1)._select(
Domain.ALL, Client.ALL,Manager.ALL,
left=[Client.on(Client.id==Domain.client_i
I just tried with the last revision (1414:da25156addab) and the
problem stills the same.
I think this is now fixed in trunk. Can you give it a try?
Massimo
On Dec 21, 9:25 am, HaM wrote:
> 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
Thanks for reporting this. It is definitively a bug and I will try fix
it today.
On Dec 21, 9:25 am, HaM wrote:
> 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 d
10 matches
Mail list logo
