CREATE INDEX considers NULL and empty string being the same in compound indices [CORE3675] #4025
Submitted by: Edson Teixeira Marques (edsontmarques)
The situation is as follows:
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.
The text was updated successfully, but these errors were encountered: