Just to put my thoughts in.

In first case the bug (ambiguous join) was fixed and actually every responsible programmer had to fix his code also, because it may have give wrong results sometimes.
In second case there is no bug in applications and no need to fix.
Very few people had ambiguous joins in their app, but nearly all apps that used IBO will be influenced by second case


Riho-Rene Ellermaa
senior programmer
Hansabank

> The identified columnlist did not deliver wrong data. In the case of the
> ambiguous join, it is imperative that bad (=faulty) code be discovered and
> fixed. In the case of the identified columnlist, there was no bug to fix.

I know but I'm surprise for this situation:
a) FB RC2, new syntax fix
b) Marco Menardi (me) had to fix lot of queries with bad join syntax and test the apps (wery time consimung)
c) none in the community was afraid about "old good apps" that can be broken by this fact
---
d) Insert problem
e) Marco Menardi (me) had to fix IBO code and recompile (5 minutes)
f) lot of community members screaming loud about "broken compatibility" of old code...

So my question: how is that??????????
Of course I'm happy for the join fix, of course I will be happy for the FB1.01 release, this is not the point. The point is: why do you need FB1.01 for "old apps" and don't worry about new join syntax check? Why upgrade database of old, already working with no problem, apps? Expecially if you don't have the code to recompile, it seems to me very very risky....
(btw, if dialect 1 there is no error for ambiguous joins, but only a warning... where and how is raised the warning? In the log file? thanks)

Thanks
Marco Menardi




[Non-text portions of this message have been removed]