CREATE INDEX considers NULL and empty string being the same in compound indices [CORE3675] #4025
Assignees
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovsummary: gbak can't activate unique key index when field is null => CREATE INDEX considers NULL and empty string being the same in compound indices |
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @dyemanovFix Version: 2.5.2 [ 10450 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Edson Teixeira Marques (edsontmarques)
Is related to CORE2709
Is duplicated by CORE3937
Votes: 1
The situation is as follows:
A table has an alternate key constraint (unique). The expression of key is composed of four distinct fields of the table. In two rows from the table, the field of order 2 (in the expression of key), has the following "values" (in quotes because is "null" is not value):null and ''(empty) respectively. That is, in the record 'n' the field is set to null, in the record n+1 the same field have the value''(empty). The other values of the other fields components of the alternate key in these records have values equal to each other. As illustrated below:
TABLE1
FIELD_A, FIELD_B, ..., FIELD_1 | FIELD_2 | FIELD_3 | FIELD_4, ..., FIELD_n
-------------------------------------------------- -----------------------------------------------
...
any, any, ..., any | any | any | any, ..., any
any, any, ..., x | null | y | z, ..., any
any, any, ..., x | | y | z, ..., any
any, any, ..., any | any | any | any, ..., any
...
-------------------------------------------------- -----------------------------------------------
('any': any values, different from each other. x, y and z can be any value, but equals in the two rows)
What happens is that when I recover a ".fbk" of this database, gbak can not activate the alternate key index coposed by FIELD_1, FIELD_2, FIELD_3 and FIELD_4, because it believes there may be a violation of the unique key constraint, however, if the TABLE1 does not have any records (no data), gbak, obviously, can recover the database and enable the constraint and, in this situation, I can insert all these records with all these values (that gbak couldn't recover previously), and there's no unique key violation.
This issue has been identified in firebird 2.5.1. We tested the same database in firebird 2.5.0 and this problem did not happen.
Commits: 161386e cf6e3d0
The text was updated successfully, but these errors were encountered: