based on the test I just ran, it reports the first one encountered only. On Jul 6, 2009, at 2:53 PM, Nicolas Williams wrote:
> On Sat, Jul 04, 2009 at 10:24:50AM +0200, Kees Nuyt wrote: >> On Fri, 03 Jul 2009 14:38:43 -0700, James Gregurich >> <bayouben...@mac.com> wrote: >> >>> >>> nuts. that makes INSERT OR REPLACE worthless if you have tables >>> dependent on one another. >>> >>> >>> Is there any way to manually get a list of records for which there >>> would be a conflict if a given record was inserted? >> >> BEGIN; >> INSERT the row, and observe any UNIQUE constraint failures. >> >> If there isn't one, the INSERT succeeded and you're done. > > Does SQLite3 report all those failuers in one attempt? Or must one > loop > to make this a robust conflict detection algorithm? > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
