>> Whether a row is deleted depends on whether the row being updated clashes >> with a current row when adding one. > > Yep. Bug or feature? Looks like a bug to me, or a least a very unwelcome > misfeature :/
It's a well documented feature: "or replace" means "if you see constraint violations while updating please delete all violating rows and then proceed with update". The same meaning it has in "insert or replace". See http://www.sqlite.org/lang_conflict.html. Pavel On Mon, May 7, 2012 at 9:35 AM, Petite Abeille <petite.abei...@gmail.com> wrote: > > On May 7, 2012, at 3:24 PM, Marc L. Allen wrote: > >> Apparently, the update is done a row at a time. > > Yep, therefore the OP inquiry about DEFERRABLE INITIALLY DEFERRED for unique > constraints. > >> Whether a row is deleted depends on whether the row being updated clashes >> with a current row when adding one. > > Yep. Bug or feature? Looks like a bug to me, or a least a very unwelcome > misfeature :/ > > _______________________________________________ > 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
