-
-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database created in Firebird 2.5.1 may cause the "IS NULL" predicate evaluated differently if used with Firebird 2.5.0 [CORE3853] #4194
Comments
Commented by: @dyemanov A complete reproducible test case is required. |
Commented by: @dyemanov Am I correct assuming that there must be a compound index involving a few fields one of those is MY_FLD? And that without such a condition, the issue doesn't manifest itself? |
Commented by: Richard Stekly (rs.) Thanks for response, I'm sorry, I'm too busy now. I'll prepare better test-case at evening. I cannot post original database, because customers data ... I have to prepare another one. CREATE TABLE TEMPLATES( + some triggers for last_update etc. |
Modified by: @dyemanovsummary: difference between 250 and 251 for "is null", but ODS is same => Database created in Firebird 2.5.1 may cause the "IS NULL" predicate evaluated differently if used with Firebird 2.5.0 Version: 2.5.0 [ 10221 ] => |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.2 [ 10450 ] assignee: Dmitry Yemanov [ dimitr ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Richard Stekly (rs.)
create or restore with recreate database in 251.
MY_TABLE - MY_FLD Varchar(31)
insert one row where MY_FLD is null
//-------
use this database in 250 engine
insert one row where MY_FLD is null
//------
select * from MY_TABLE where MY_FLD is null
result set contain only one row, written by the same version of engine.
bug is fixed after backup-restore with recreate
I mean ODS version shoud be different in this case, not 11.2 - 11.2, I do'nt have any other version protection.
Commits: 161386e cf6e3d0
The text was updated successfully, but these errors were encountered: