🚀 go-pugleaf

"Massimiliano Trezzi" <support_leavethis_@intesanet.it> wrote in message
news:4844ec75$1@newsgroups.borland.com...
> 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.

Exactly. The current error message is total bogus and doesn't help the user
at all.

If the error is caused by the mixed join syntax (which shouldn't be a
problem
at all), then it should be a clear error message.

Nevertheless, the syntax IS valid (in SQL 92) and should be supported, after
all, it is parsed by InterBase, but not properly executed. This is NOT a
user
problem, but an InterBase problem.


-- 
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com