Unique index could be created on non-unique data [CORE5161] #5444
Labels
affect-version: 2.1.7
affect-version: 2.5.3 Update 1
affect-version: 2.5.3
affect-version: 2.5.4
affect-version: 2.5.5
affect-version: 3.0 Beta 1
affect-version: 3.0 Beta 2
affect-version: 3.0 RC1
affect-version: 3.0 RC2
component: engine
fix-version: 2.5.6
fix-version: 3.0.0
fix-version: 4.0 Alpha 1
priority: major
qa: done successfully
type: bug
Submitted by: Polesov (polesov)
Detected the error of violation of uniqueness of the primary key.
Check the database using GFIX program error is not detected.
Operation BACKUP/RESTORE runs without error, but a duplicate primary key remains.
Recreation of the primary key passes without error, but the duplicate remains.
Table structure:
CREATE DOMAIN D_ID AS INTEGER NOT NULL;
CREATE DOMAIN D_GUID AS VARCHAR(36) CHARACTER SET WIN1251 COLLATE WIN1251;
CREATE TABLE EMPLOYES (
ID D_ID NOT NULL,
GUID D_GUID NOT NULL
);
ALTER TABLE EMPLOYES ADD CONSTRAINT PK_EMPLOYES PRIMARY KEY (ID);
CREATE INDEX EMPLOYES_IDX_GUID ON EMPLOYES (GUID);
Commits: b0981f1 28709e9 33e65f6 e891e0f
The text was updated successfully, but these errors were encountered: