ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zhenya Stanilovsky <arzamas...@mail.ru.INVALID>
Subject [SQL] Correct index usage with primary key constraint.
Date Wed, 26 Aug 2020 13:00:24 GMT

Folks, want to pay your attention that after [1] was merged into master, primary key index
usage became predictable and correct and as a consequence old behavior was broken.
 
for example table creation:
CREATE TABLE PUBLIC.T1 (F1 VARCHAR, F2 VARCHAR, F3 VARCHAR, CONSTRAINT PK PRIMARY KEY (F2,
F1))
in the old ver columns (F2, F1) were reordered, thus request :
select … from PUBLIC.T1 WHERE F2 > … will not use primary key and index at all.
after fix was merged primary key index used correctly.
 
[1] https://issues.apache.org/jira/browse/IGNITE-13376
 
 
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message