Mike _ wrote: > The trigger documentation says: "An ON CONFLICT clause may be specified as > part of an UPDATE or INSERT action within the body of the trigger. However > if an ON CONFLICT clause is specified as part of the statement causing the > trigger to fire, then conflict handling policy of the outer statement is > used instead."
Therefore, you should not ever use INSERT OR ... in a trigger. > Is this because the "ON UPDATE CASCADE" action is considered to be the > statement causing the trigger to fire, This is the only thing that updates the child table. > meaning the default conflict handling policy of ABORT is used? Apparently. > If so, is there any way to write something like "ON UPDATE CASCADE OR > REPLACE"? No. You have to do it by hand. Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
