Given that this issue has existed for years, and many simple workarounds
are known, I doubt it will change any time soon. If you want to use
SQLite, you have to rewrite the queries. The benefit of changing the
generated SQL is that it will work on all the databases you mentioned.
The sqlite source code is available. You can modify it as see you fit.
--- "Bruno S. Oliveira" <[EMAIL PROTECTED]> wrote:
> As I told you, I know how to avoid this. But I can't rewrite these
> queries. That's my problem...
>
> Thanks for your attention.
>
> Regards,
> Bruno
>
> On 8/17/07, Joe Wilson <[EMAIL PROTECTED]> wrote:
> > SELECT t_dados.id
> > FROM Points1 LEFT JOIN t_dados ON Points1.object_id = t_dados.id
> > ORDER BY t_dados.id, Points1.geom_id;
> >
> > --- "Bruno S. Oliveira" <[EMAIL PROTECTED]> wrote:
> > > I'm having problems with the following query (and, in general, in
> > > queries using left joins):
> > >
> > > [EMAIL PROTECTED]:~$ sqlite3 parana
> > > SQLite version 3.4.1
> > > Enter ".help" for instructions
> > > sqlite> SELECT t_dados.id FROM (Points1 LEFT JOIN t_dados ON
> > > Points1.object_id = t_dados.id) WHERE 1 = 1 AND 1 = 1 ORDER BY
> > > t_dados.id, Points1.geom_id;
> > > SQL error: no such column: t_dados.id
____________________________________________________________________________________
Choose the right car based on your needs. Check out Yahoo! Autos new Car
Finder tool.
http://autos.yahoo.com/carfinder/
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
