 dan
|
ae0931edae
|
Add some tests that involve BEFORE UPDATE or BEFORE DELETE triggers messing with the row being updated or deleted. SQLite behaviour in this scenario is undefined, so the tests just check that the behaviour is relatively sane and there are no crashes.
FossilOrigin-Name: 9a4c59a2ddd0df2d9425097004b450a6685f2147
|
2009-09-09 15:06:10 +00:00 |
|
|
dan
|
e0af83aca6
|
Combine the OP_Statement and OP_Transaction opcodes.
FossilOrigin-Name: aec9dbd8d21c55c3945287a3dfa55d3ed168f977
|
2009-09-08 19:15:01 +00:00 |
|
|
dan
|
2283d46cd6
|
If recursive-triggers are enabled, fire DELETE triggers if database rows are removed as a result of OR REPLACE conflict resolution.
FossilOrigin-Name: 85cb0c94a63eda5f059ebe40887c7af9b4869893
|
2009-09-08 15:55:15 +00:00 |
|
|
drh
|
417168ade2
|
Add the SQLITE_LIMIT_TRIGGER_DEPTH option to sqlite3_limit().
FossilOrigin-Name: d7dc8b433691745b3842282569f1573d1e057963
|
2009-09-07 18:14:02 +00:00 |
|
|
dan
|
5bde73c4eb
|
Change "PRAGMA disable_recursive_triggers" to "PRAGMA recursive_triggers". Also a fix for compiling with OMIT_TRIGGER defined.
FossilOrigin-Name: e016cca36390451d5d1c6e0d1b3cdbd6d869be1a
|
2009-09-01 17:11:07 +00:00 |
|
|
dan
|
436355a091
|
Add new test script triggerC.test.
FossilOrigin-Name: a2a062a4b52f45af85c195582a36d1b76d2675db
|
2009-09-01 16:19:19 +00:00 |
|