Indices on computed fields are broken after restore (all keys are NULL) [CORE5118] #5402
Labels
affect-version: 2.5.0
affect-version: 2.5.1
affect-version: 2.5.2
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.0
affect-version: 4.0 Initial
fix-version: 2.5.9
fix-version: 3.0.5
fix-version: 4.0 Beta 1
priority: blocker
qa: done successfully
type: bug
Submitted by: CHENAVIER Gérald (gchenavier)
Is related to CORE4673
Duplicates CORE2440
Votes: 1
No problem in 2.5.2, it is regression :
The Select with order by computed col return 0 line.
Reproduct :
CREATE TABLE T1 (IDT1 INTEGER, NOMT1 VARCHAR(10), PRENOMT1 VARCHAR(10) , NOMPRENOMT1 COMPUTED BY (NOMT1 || ' ' || PRENOMT1));
CREATE TABLE T2 (IDT2 INTEGER);
INSERT INTO T1 (IDT1, NOMT1, PRENOMT1)VALUES (1, 'NOM1', 'PRENOM1');
INSERT INTO T1 (IDT1, NOMT1, PRENOMT1)VALUES (2, 'NOM2', 'PRENOM2');
INSERT INTO T1 (IDT1, NOMT1, PRENOMT1)VALUES (3, 'NOM3', 'PRENOM3');
INSERT INTO T2 (IDT2)VALUES (0);
CREATE INDEX YYT1 ON T1 COMPUTED BY (NOMPRENOMT1);
make Backup/restore in 2.5.5
select a.IDT1, a.NOMT1, a.NOMPRENOMT1 from T1 a order by 3
-> return 0 line
select a.IDT1, a.NOMT1, a.NOMPRENOMT1 from T1 a order by 2
-> its ok
Commits: dfc0259 fea7c61 a741300
The text was updated successfully, but these errors were encountered: