The documentation for ON CONFLICT REPLACE has this clause: "When this conflict resolution strategy deletes rows in order to satisfy a constraint, it does not invoke delete triggers on those rows. This behavior might change in a future release."
Are there any plans to actually change this behavior? I'm looking at using REPLACE instead of some existing UPDATE statements to simplify the SQL and processing, but if in the future it starts invoking DELETE triggers it would break my app. Thanks, Sam ----------------------------------------------------------------- We're Hiring! Seeking passionate Flex, C#, or C++ (RTSP, H264) developer in the Washington D.C. Contact [EMAIL PROTECTED] _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
