Subject | Some further IBO/FB1 incompatibility considerations |
---|---|
Author | mmenaz |
Post date | 2002-03-14T16:22:26Z |
After two day from the discovery that the Insert statements automatically created by IBO are incompatible with the new FB1 (or vice versa ;), I think that this problem will not be of big damage because:
a) The IBO fix is very little (two lines) and can be made by Jason on the old code that is already supported (3.6something), or by any registered user
b) this will not prevent the adoption of FB1 more than the new control on syntax in column name in joins. I had a lot of queries with joins and columns not table qualified (ambiguous between two or more tables), so when I adopted FB I had to fix and recompile my code. In this situation, adding a) fix is a snap.
So, since b) is out of question (I mean, FB will not revert to a confusing syntax), a) should be a minor issue for IBO users, or am I missing something? Do you really think your customers are able to update their database by themselves? And, are they really using Fb_RC2? or more probably they are using Interbase... so a) problem?
Regards
Marco Menardi
a) The IBO fix is very little (two lines) and can be made by Jason on the old code that is already supported (3.6something), or by any registered user
b) this will not prevent the adoption of FB1 more than the new control on syntax in column name in joins. I had a lot of queries with joins and columns not table qualified (ambiguous between two or more tables), so when I adopted FB I had to fix and recompile my code. In this situation, adding a) fix is a snap.
So, since b) is out of question (I mean, FB will not revert to a confusing syntax), a) should be a minor issue for IBO users, or am I missing something? Do you really think your customers are able to update their database by themselves? And, are they really using Fb_RC2? or more probably they are using Interbase... so a) problem?
Regards
Marco Menardi