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
danielk1977
96d48e963a
Cause incremental-blob read/write operations lock shared-cache tables in the same way as normal SQL read/writes. Add complex assert statements to make sure tehe correct shared-cache locks are held when accessing the database. Eliminate some redundant checks from btree.c. (CVS 6830)
...
FossilOrigin-Name: f17ef37897da9bcaf20b5acdce6840522c0a0b16
2009-06-29 06:00:37 +00:00
danielk1977
404ca07578
Add the sqlite3_unlock_notify() API. (CVS 6348)
...
FossilOrigin-Name: b649a6cc5bfefddd6a04b1183647d2923e0a0daa
2009-03-16 13:19:36 +00:00
danielk1977
740ed546fc
Change one of the test cases in incrblob2.test to avoid allocating a 10MB block of heap memory. (CVS 5764)
...
FossilOrigin-Name: 83b7dd737a16555b9eb4ad9faacac3d705b0a90e
2008-10-03 08:44:54 +00:00
danielk1977
986fbb8e30
Remove an assert() that was failing if there were any open incremental blob handles when a statement transaction was rolled back. (CVS 5326)
...
FossilOrigin-Name: f66491ab2ba3645d4e44e33ec6fa0ab94b2989be
2008-06-28 15:33:24 +00:00
danielk1977
0cdc022e88
Fix handling of "x IN (...)" and "x NOT IN (...)" expressions when the set contains an SQL NULL value. (CVS 5314)
...
FossilOrigin-Name: d45a97be71fa61ab4a692bd807ab762130f7f5b9
2008-06-26 18:04:03 +00:00
drh
3f994d06ff
Test enhancements, especially to the new compound-SELECT merge logic. (CVS 5305)
...
FossilOrigin-Name: edf7f518361902924105142a8c67b898ba7d532f
2008-06-25 14:31:53 +00:00
danielk1977
dfdf9844aa
Fix a recently introduced resource leak in test file incrblob2.test (forgot to close a blob handle). (CVS 5223)
...
FossilOrigin-Name: 88e1c6092e48c860950d3437f264785243bb67ed
2008-06-16 14:36:01 +00:00
danielk1977
99e925da51
Fix a problem with the incremental blob API. sqlite3_blob_open() was always reading the data for the leftmost column of the row that the opened blob was stored in. If this column happened to contain a (the) large blob, sqlite would make a large memory allocation to read the data into. Which defeats the purpose of using incremental blobs. (CVS 5222)
...
FossilOrigin-Name: 1b9478da2f421c1270e76297324fff8037d2f231
2008-06-16 14:19:57 +00:00
danielk1977
5e982b1c38
Add another test to incrblob2.test. This test failed to reveal any new bugs. (CVS 5214)
...
FossilOrigin-Name: 20d8ea45afcddf22632c3de984147826d0616d3f
2008-06-12 14:42:06 +00:00
danielk1977
3588ceb868
Invalidate sqlite3_blob* handles whenever an SQL statement is used to delete or modify the rows containing the open blob. Previously, modifying the table containing the open blob in any way invalidated the handle. This was too restrictive. (CVS 5199)
...
FossilOrigin-Name: e339c91f8718482ce74fc53781091db95e69d4c3
2008-06-10 17:30:26 +00:00
danielk1977
55edca5c17
Add test file incrblob2.test to test opening two blob handles on a single database blob. (CVS 5196)
...
FossilOrigin-Name: c1d877feb530b5cdaad55da3dbbb7c2596a10c49
2008-06-09 15:51:26 +00:00
