mirrors/sqlite
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
28,772 Commits 1,487 Branches 166 Tags 416 MiB
d0be4a781e
Commit Graph

22 Commits

Author SHA1 Message Date
drh
175b8f06f7 Remove support for STAT3. The sqlite_stat3 tables are ignored, if they 
exist.  STAT4 continues to work as it always has, and as it is a superset of
STAT3 is the recommended replacement.

FossilOrigin-Name: 1e17ea2fd1df4ad49138c787c8fe3207dd0c25c93f9001d52a9b69f8c12e841c
 2019-08-08 15:24:17 +00:00
dan
b84b38fd89 Add test cases to improve coverage of VDBE branches. Still some to go. 
FossilOrigin-Name: 4cef609d61de272cfdc2b39e1d49c7cd56ec834086bd63095116ff98f4d402bd
 2019-04-04 17:58:34 +00:00
dan
16dd3985f0 Fix a segfault caused by using the RAISE function incorrectly (library now 
returns an error instead of crashing).

FossilOrigin-Name: ddf06db702761d663119d508afe21d7dfebe963d576bb42fc2f2024205ab86f8
 2018-12-20 15:04:38 +00:00
dan
464083544e Ensure that tables names are dequoted exactly once by the trigger logic. 
FossilOrigin-Name: 9d887b92f8086961e045f8acb9ee7a443796d411
 2015-04-21 16:38:49 +00:00
drh
f9c8ce3ced Standardize the error messages generated by constraint failures to a format 
of "$TYPE constraint failed: $DETAIL".  This involves many changes to the
expected output of test cases.

FossilOrigin-Name: 54b221929744b1bcdbcc2030fef2e510618afd41
 2013-11-05 13:33:55 +00:00
dan
f78baafe41 Apply the same restrictions on constant refactoring to statements within a trigger program as top-level statements. Candidate fix for [ae3c5670b6]. 
FossilOrigin-Name: 0c31a46801746191d1a53332d75beda880fe1fd7
 2012-12-06 19:37:22 +00:00
drh
3f4d1d1b02 Attempt to use a covering index even on a full table scan, under the theory 
that the index will be smaller and require less disk I/O and thus be faster.

FossilOrigin-Name: cfaa7bc12847a7006ccc93815f2395ad5259744a
 2012-09-15 18:45:54 +00:00
mistachkin
fda06befd5 Add retry logic for AV defense to winOpen. Also, refactor test suite to allow the key Tcl file operations (e.g. copy and delete) to be retried. 
FossilOrigin-Name: 9007586fdabed8dbcc78581ea9821cfd1f9a4c8c
 2011-08-02 00:57:34 +00:00
shaneh
f9032cbc2d Adjust a test case in triggerC.test to handle non-default SQLITE_MAX_TRIGGER_DEPTH settings. 
FossilOrigin-Name: f14339c54bdeabc68c1e05b2c63ee95226f184e0
 2011-06-22 14:43:59 +00:00
shaneh
35913a49db Adjust some test cases in triggerC.test to handle non-default SQLITE_MAX_TRIGGER_DEPTH settings. 
FossilOrigin-Name: 9d6c6129fd8be42c164f14bb90011b252c1f2c46
 2011-04-17 00:55:13 +00:00
dan
271065704c Avoid recursive calls to sqlite3VdbeMemRelease() when deleting VM frames used by trigger programs. 
FossilOrigin-Name: 119ffe955eb1e8016cb8131a63bd17557f395f3f
 2010-12-01 08:04:47 +00:00
dan
98530cac13 Test that it is possible to drop a trigger while there are active statements belonging to the same connection. 
FossilOrigin-Name: d4ec61e2547200aa92a26c1f270682ed67edc241
 2010-08-14 05:04:47 +00:00
dan
7ba4597135 Do not crash when compiling an "INSERT INTO tbl DEFAULT VALUES" when tbl has either BEFORE or INSTEAD OF triggers attached to it. Ticket [f3162063fd]. 
FossilOrigin-Name: ca359a3e8048bd11605c41c4b48134c0343e543b
 2010-03-30 12:40:32 +00:00
dan
bb5f168f2e Move [7d30880114] to the trunk. Add optimizations to reduce the number of opcodes used for BEFORE UPDATE triggers. 
FossilOrigin-Name: 1b7c5250ccb63182324bfc3f1ea28f17b6db357a
 2009-11-27 12:12:34 +00:00
dan
07fcc26824 Update triggerC.test to match the change to the way the trigger-recursion limit is handled. 
FossilOrigin-Name: 5806925283b889867567c4ad92518bad000e9d9d
 2009-10-08 06:24:41 +00:00
drh
3991bb0dee When coding a trigger, assume that the "oldmask" requires all columns until 
we know otherwise.  That pessimistic assumption assures that all necessary
parameters are available on a cascading delete trigger.
Ticket [e25d9ea771f]

FossilOrigin-Name: 03e464be51a1c36fc02cf31178ae91f736dfddd6
 2009-09-17 00:41:19 +00:00
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