You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this column is joined in the program with integer columns by inner joins
if the ODS of the database is before 11.0 we always get good results for these joins
when making an backup of these databases and restoring it as an ODS 11.0 these joins give unpredicatable results
if we use an cast( as integer) on the varchar(5) column it works ok.
Is it possible to make this as it worked before.
I remeber i had the same problem before when the first beta's of firebird 2 engine where released
I then also submitted an post.
the first response was that this was made to improve the engine and the problem wouldn't be fixed
Later i received an mail that that it would be fixed because it broke many applications using firebird
The text was updated successfully, but these errors were encountered:
I have a feeling that it's not about ODS 10 vs ODS 11, but about FB v2.1 vs prior versions. After a few bugfixes that disabled index based joins for incompatible data types, CORE1274 had become visible and it looks very similar to what is reported in this ticket.
Submitted by: Rene Pijnacker (rene.pijnacker_nocore.nl)
In our application we have an table containing
and string column of varchar(5)
this column is joined in the program with integer columns by inner joins
if the ODS of the database is before 11.0 we always get good results for these joins
when making an backup of these databases and restoring it as an ODS 11.0 these joins give unpredicatable results
if we use an cast( as integer) on the varchar(5) column it works ok.
Is it possible to make this as it worked before.
I remeber i had the same problem before when the first beta's of firebird 2 engine where released
I then also submitted an post.
the first response was that this was made to improve the engine and the problem wouldn't be fixed
Later i received an mail that that it would be fixed because it broke many applications using firebird
The text was updated successfully, but these errors were encountered: