And what about NULL values? > All fields would match in an existing record compared to that of a > proposed new record. That help? > > On 10/21/2016 4:49 PM, Simon Slavin wrote: > > On 21 Oct 2016, at 10:46pm, Rick Kohrs <rick.ko...@ssec.wisc.edu> wrote: > > > >> I want to make sure that I do not insert a new record if ALL of the > variables match. I can potentially have 3 systems writing to the same > database and I don't want duplicate records > >> > >> sqlCommand = """ > >> CREATE TABLE himawari_db ( > >> dateTime TEXT, > >> filename TEXT, > >> satID TEXT, > >> year INT, > >> month INT, > >> day INT, > >> hour INT, > >> minute INT, > >> band INT, > >> coverage TEXT, > >> region INT, > >> segment INT, > >> server TEXT);""" > >> try: > >> satDB.execute(sqlCommand) > >> try: > >> dbConnect.commit() > > How do you define "duplicate" ? What field or fields of a new record > have to be the same as an existing one for you to want "reject that one, > it's a duplicate of one already there" ? > > > > Simon. > > _______________________________________________ > > sqlite-users mailing list > > sqlite-users@mailinglists.sqlite.org > > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
