On Mon, Dec 8, 2014 at 9:01 AM, Dan Kennedy <danielk1...@gmail.com> wrote: > You could hack SQLite to do enforce unique constraints the same way as FKs. > When adding an entry to a UNIQUE index b-tree, you check for a duplicate. If > one exists, increment a counter. Do the opposite when removing entries - > decrement the counter if there are two or more duplicates of the entry you > are removing. If your counter is greater than zero at commit time, a UNIQUE > constraint has failed. > > I suspect there would be a non-trivial increase in the CPU use of UPDATE > statements though.
Well, it'd be an option which, when not used, ought to cost very few additional unlikely branches. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
