🚀 go-pugleaf

Hi,
it's me again!

tell this to your bosses:

the problem we have, is that we made a lot of projects with Oracle Hyperion 
business untelligence suite (the old BrioQuery), and we developed them on 
Interbase 5.6; now we migrated a lot of our customers to Interbase 2007 and 
we discovered that these projects don't work because Hyperion generate the 
queries with implicit joins for inner join and explicit joins for outer 
ones.
I don't think I'm the only one with this problem and I don't think you like 
have this defect and remember that this syntax is valid in SQL-92.
Maybe Oracle could change something in its product, but their database works 
fine in this context and I think they don't mind of Interbase, because, I 
repeat, this syntax is standard in SQL-92.

Hi,
Massimiliano.


"Bill Todd [TeamB]" <no@no.com> ha scritto nel messaggio 
news:48497398@newsgroups.borland.com...
> Massimiliano Trezzi wrote:
>
>>    It's a bug and it's clear that it's not designed to be so.
>
> "As designed" means as designed by the software engineers responsible
> for the product. It may not work the way you want it to and it may not
> work the way the SQL standard says it should but, as Quinn stated, it
> does work the way the R&D team intended. Therefore, this behavior is
> not a bug. If you disagree with this please look in any dictionary of
> software engineering terms for the definition of a bug.
>
> I certainly agree with you that IB should be changed so that SQL that
> does not execute correctly either does not execute at all or that it
> does execute correctly. I do disagree with you in that I think the best
> fix for IB is to generate an error message and not execute the SQL.
> There are too many move valuable things that R&D can spend time on to
> invest their time in making IB support mixed mode joins.
>
> -- 
> Bill Todd (TeamB)