> On Oct 21, 2016, at 2:46 PM, Rick Kohrs <rick.ko...@ssec.wisc.edu> wrote: > > INSERT or IGNORE does not seem to be working as expected.
The “or IGNORE” part describes what happens if there’s a conflict that would otherwise cause the INSERT to fail. Your schema doesn’t declare any column or columns as being UNIQUE, so SQLite sees no conflict in adding identical rows. If you want to prevent identical rows it looks like you’d need to add a clause to your table like “UNIQUE (dateTime, filename, … server)”, i.e. listing all of the columns. (For performance’s sake it would help if you could identify a smaller number of columns that need to be unique.) —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
