🚀 go-pugleaf

I'm sorry, but I have to say that I disagree
    It's a bug and it's clear that it's not designed to be so.

I include from another post of mine:

> 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.

If you say "we won't fix it because it would be very expensive and we think 
it's unimportant" I can say nothing, but I can't accept you say it's not a 
bug and you planned so.
I reported the problem in QC, it was promoted to internal database and kept 
opened. I'd like to know what it's going to happen to this issue.

Thank you in advance,
Massimiliano Trezzi




"Bill Todd [TeamB]" <no@no.com> ha scritto nel messaggio 
news:48494656$1@newsgroups.borland.com...
> Massimiliano Trezzi wrote:
>
>> and now what are you going to do?
>> I think that if you won't fix it, I must know it.
>> I don't pretend you make a service pack for this, but knowing  if
>> you'll resolve this for the next service pack or release, it's
>> important.
>
> I don't understand your question. Quinn Wildman, who is a CodeGear
> employee, already made the following reply earlier in this thread.
>
> "R&D has determined SQL with implicit and explicit joins is bad SQL and
> therefore is not supported."
>
> Therefore, if you are asking if InterBase will be changed to support
> SQL statements that include both implicit and explicit joins the answer
> is no. However, you replied to my post in which I said that IB should
> generate an error and not execute the query. If you are asking if the
> error message will be added in a future version the answer is that no
> one knows. If you want that to happen enter a bug report in QC
> indicating that an error should be returned when a statement includes
> both implicit and explicit joins and R&D will look at it when they
> begin fixing bugs in the next version. It is not likely that anyone
> will make a firm commitment now.
>
> -- 
> Bill Todd (TeamB)