🚀 go-pugleaf

I never wrote manually a query like this, but some _good_ tools do it!

I think this is a bug beacuse:
    SQL-92 should accept this syntax: it's bad but it's correct!
    all other good databases work with this syntax,
    you can have the same problem making a good query with implicit joins 
made over some view with explicit outer joins (have I to look inside the 
view before building the query?)
    In Interbase 5.6 this worked

This is not as designed because:
    it happens when fetching records not after parsing the query,
    the error is not systematic, but it comes only with outer joins and only 
in some circustances
    the message is clearly related to some internal code (from sql we do not 
manage fetching)

If it was designed as this,  I'd expect a message like this "You cannot mix 
explicit joins with implicit joins" and it should be systematic.

I hope you understand my bad English, and I hope you understand that 
Interbase should be better without this unpredictable behaviour!

Hi,
Massimiliano Trezzi.,


With Delphi I can write ugly code,

"Bill Todd [TeamB]" <no@no.com> ha scritto nel messaggio 
news:483eb8db$1@newsgroups.borland.com...
> Massimiliano Trezzi wrote:
>
>> This is not the result of an accurate design, but this is a bug:
>
> This is not a bug. A bug is something that does not work as designed.
> The only thing that R&D should do in this case is generate an error and
> not execute the query.
>
> -- 
> Bill Todd (TeamB)