I think the point is that attempting to create the unique index should fail
(with an error) and the index not be created rather than creating a unique
index with duplicates (or whatever it is doing) causing subsequent queries to
return incorrect results.
>On Wed, 30 Jul 2014 09:10:29 +0400
On Wed, 30 Jul 2014 09:10:29 +0400
Pavel Pimenov wrote:
> CREATE TABLE fly_hash_block(tth_id integer PRIMARY KEY NOT NULL, tth
> number NOT NULL);
> INSERT INTO fly_hash_block VALUES(1,1);
> INSERT INTO fly_hash_block VALUES(2,2);
> INSERT INTO fly_hash_block
hi
C:\!dc-db\db-sqlite-corrupt\db-uniq-bug>sqlite3 --version
3.8.5 2014-06-04 14:06:34 b1ed4f2a34ba66c29b130f8d13e9092758019212
C:\!dc-db\db-sqlite-corrupt\db-uniq-bug>sqlite3.exe FlylinkDC.sqlite
0
SQL> CREATE TABLE fly_hash_block(tth_id integer PRIMARY KEY NOT NULL, tth
number NOT NULL);
3 matches
Mail list logo