Re: Cascaded delete unexpectedly triggered by upsert (Docs Update?)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Cascaded delete unexpectedly triggered by upsert (Docs Update?)

Keith Medcalf

On Tuesday, 7 January, 2020 17:05, Simon Slavin <[hidden email]> wrote:

>On 8 Jan 2020, at 12:00am, Michael Kappert <[hidden email]> wrote:

>> REPLACE INTO

>REPLACE INTO is an alias for INSERT OR REPLACE.  So you should assume
>that the command will do either an INSERT or a REPLACE.

>See the notes about REPLACE on this page:

><https://sqlite.org/lang_conflict.html>
>
>Is the behaviour you're seeing consistent with that documentation ?

Note that the information contained on here:

https://sqlite.org/pragma.html#pragma_recursive_triggers

is inconsistent with the information contained here:

https://sqlite.org/limits.html#max_trigger_depth


Should not the "Recursive triggers may be turned on by default in future versions of SQLite." be replaced with the more explicit "Recursive triggers default to on starting with version 3.7.0 (2009-09-11)."

--
The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume.



_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users