Hello, I am migrating some older version of H2(1.7.154) database into new last usable (and marked stable)(1.7.175) trough linked tables. Migration stopped on constraint violation on new database which is caused by duplicate data in old one. Was that bug fixed in newer version or should I send db with duplicate values to further investigation? Following selects are all issued on old version of database:
select * from Stock_history where element_id = 62 and history_date = '2016-07-19'; STORE_ID <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> ELEMENT_ID <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> CUR <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> HISTORY_DATE <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> 1 62 79.0000 2016-07-19 1 62 79.0000 2016-07-19(2 rows, 0 ms) select * from information_schema.indexes where table_name = 'STOCK_HISTORY'; TABLE_CATALOG <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> TABLE_SCHEMA <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> TABLE_NAME <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> NON_UNIQUE <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> INDEX_NAME <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> ORDINAL_POSITION <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> COLUMN_NAME <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> CARDINALITY <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> PRIMARY_KEY <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> INDEX_TYPE_NAME <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> IS_GENERATED <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> INDEX_TYPE <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> ASC_OR_DESC <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> PAGES <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> FILTER_CONDITION <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> REMARKS <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> SQL <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> ID <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> SORT_TYPE <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> CONSTRAINT_NAME <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> INDEX_CLASS <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> DB PUBLIC STOCK_HISTORY TRUE CONSTRAINT_INDEX_1B 1 STORE_ID 0 FALSE INDEX TRUE 3 A 0 CREATE INDEX PUBLIC.CONSTRAINT_INDEX_1B ON PUBLIC.STOCK_HISTORY(STORE_ID) 100 0 CONSTRAINT_1B org.h2.index.PageBtreeIndex DB PUBLIC STOCK_HISTORY TRUE CONSTRAINT_INDEX_1B3 1 ELEMENT_ID 0 FALSE INDEX TRUE 3 A 0 CREATE INDEX PUBLIC.CONSTRAINT_INDEX_1B3 ON PUBLIC.STOCK_HISTORY(ELEMENT_ID) 102 0 CONSTRAINT_1B3 org.h2.index.PageBtreeIndex DB PUBLIC STOCK_HISTORY FALSE PRIMARY_KEY_1B 1 STORE_ID 0 TRUE PRIMARY KEY TRUE 3 A 0 CREATE PRIMARY KEY PUBLIC.PRIMARY_KEY_1B ON PUBLIC.STOCK_HISTORY(STORE_ID, ELEMENT_ID, HISTORY_DATE) 104 0 CONSTRAINT_1B38 org.h2.index.PageBtreeIndex DB PUBLIC STOCK_HISTORY FALSE PRIMARY_KEY_1B 2 ELEMENT_ID 0 TRUE PRIMARY KEY TRUE 3 A 0 CREATE PRIMARY KEY PUBLIC.PRIMARY_KEY_1B ON PUBLIC.STOCK_HISTORY(STORE_ID, ELEMENT_ID, HISTORY_DATE) 104 0 CONSTRAINT_1B38 org.h2.index.PageBtreeIndex DB PUBLIC STOCK_HISTORY FALSE PRIMARY_KEY_1B 3 HISTORY_DATE 0 TRUE PRIMARY KEY TRUE 3 A 0 CREATE PRIMARY KEY PUBLIC.PRIMARY_KEY_1B ON PUBLIC.STOCK_HISTORY(STORE_ID, ELEMENT_ID, HISTORY_DATE) 104 0 CONSTRAINT_1B38 org.h2.index.PageBtreeIndex DB PUBLIC STOCK_HISTORY TRUE STOCKHISTORY_HISTORYDATEINDEX 1 HISTORY_DATE 0 FALSE INDEX FALSE 3 A 0 CREATE INDEX PUBLIC.STOCKHISTORY_HISTORYDATEINDEX ON PUBLIC.STOCK_HISTORY(HISTORY_DATE) 106 0 *null* org.h2.index.PageBtreeIndex(6 rows, 0 ms) select * from INFORMATION_SCHEMA.settings; NAME <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> VALUE <http://192.168.1.63:8082/query.do?jsessionid=2500ffc60a24b0dc655147e64e1e8eb6#> CREATE_BUILD 154 info.BUILD_ID 172 But when I issue insert constraints work correctly: insert into stock_history values (1, 62, 79.0000,'2016-07-19'); Unique index or primary key violation: "PRIMARY_KEY_1B ON PUBLIC.STOCK_HISTORY(STORE_ID, ELEMENT_ID, HISTORY_DATE)"; SQL statement: Sincerely Petr Holik -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
