On Thu, Mar 8, 2012 at 11:56 AM, Nico Williams <[email protected]> wrote: > On Thu, Mar 8, 2012 at 11:47 AM, Marc L. Allen > <[email protected]> wrote: >> But this is extremely inefficient as well. Since each record is, in fact, >> an update, you're actually performing a delete/insert for each record, >> activating any recursive triggers you have as well. On top of that, any >> UPDATE trigger would not fire. Now, if it were an 'insert or update' it >> might better. > > Well, it's not inefficient in the same way as your UPDATE statement in > your original post. I do think that INSERT OR REPLACE should fire > insert or update triggers, not delete and/or insert triggers -- I > really want a pragma by which to request this. And it might not be > inefficient at all.
Specifically I want this behavior only when the replacing row has the same primary key and/or rowid as the old one. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
