got it. :-)
On May 27, 8:15 am, Nico de Groot wrote:
> Hi Massimo,
>
> Same problem exists in SQLserver (not surprising, uses the same code).
> I think that arguably the best solution would be to change the current
> JOIN X,Y ... WHERE [join condition] into X INNER JOIN Y ON [join
> condition]. T
Hi Massimo,
Same problem exists in SQLserver (not surprising, uses the same code).
I think that arguably the best solution would be to change the current
JOIN X,Y ... WHERE [join condition] into X INNER JOIN Y ON [join
condition]. That would be a bigger patch...
For now I've used the patch by Ale
I have no objection to changing this. Can you want to submit a patch
and help with testing?
On May 13, 4:16 pm, salbefe wrote:
> Hello,
>
> Only a question, athttp://pypi.python.org/pypi/ibm_db/there is a
> Python DBI driver for DB2. Why web2py is still using ODBC?? Will not
> be better to use th
Hello,
Only a question, at http://pypi.python.org/pypi/ibm_db/ there is a
Python DBI driver for DB2. Why web2py is still using ODBC?? Will not
be better to use this one instead of pyodbc??
Thanks
On 11 mayo, 16:27, mdipierro wrote:
> Thank you. will look into it.
>
> Massimo
>
> On May 11, 6:31
Thank you. will look into it.
Massimo
On May 11, 6:31 am, Alexey Nezhdanov wrote:
> Hi.
> I've come across another subtle problem with web2py's DAL running over IBM
> DB2 database.
> DB2 requires the left table to immidiatedly preceed the 'left outer join'
> keyword.
> IOW:
> select * from a, b
5 matches
Mail list logo
