On May 19, 2017 1:21:49 PM EDT, Paul Sanderson <sandersonforens...@gmail.com> wrote: >Is the autoindex associated when using unique with an integer primary >key >definition redundant? > >I have seen a number of DBs/tables created in the following form: > >Create table test(id integer unique primary key); > >Insert into test values (1); > >Insert into test values (2); > >Insert into test values (3); > >The table is created and populated as expected, but an >sqlite_autoindex_test_1 is also created with content that mirrors >exactly >the rowid/id. > >Is the autoindex redundant and is this an opportunity for optimisation? > > >Using 3.18.0 > >Paul >www.sandersonforensics.com >skype: r3scue193 >twitter: @sandersonforens >Tel +44 (0)1326 572786 >http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit >-Forensic Toolkit for SQLite >email from a work address for a fully functional demo licence >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
A primary key is by definition unique, so the unique constraint is needless duplication. Note, too, that the primary key is only an alias for the rowid when using the formulation "integer primary key" exactly. -- J. King _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
