write cursors can be open at the same time now, but a write cannot occur
as long as one or more read cursors are open.
Before this change, one or more read cursors could be open on a table,
or a single write cursor, but not both. Both policies have the same
desirable effect: they prevent writes to a table while a sequential scan
of that table is underway. But the new policy is a little less restrictive.
Both policies prevent an UPDATE from occurring inside a SELECT (which is
what we want) but the new policy allows a SELECT to occur inside an
UPDATE. (CVS 739)
FossilOrigin-Name: 8c2a0836980341faa479cfe6c716409e6057367d
still honor the busy callback and should return an error message together
with the SQLITE_BUSY result code. (CVS 733)
FossilOrigin-Name: 78a0229a7e5e33fe642847381f5514e6ec30f29f
to make cursor numbers right on nested subqueries. Also added OP_Gosub and
OP_Return but have not actually used them for anything yet. (CVS 727)
FossilOrigin-Name: c602603e7cd8dc5c8bb9db2748eacab650de5bf0
statements - it was being included as part of the datatype. This fixes
the problem. (CVS 722)
FossilOrigin-Name: 39bd52d33029233d4b22df08975e9ef3c74c260f
use an index for sorting. It has to sort as a separate operation after
the GROUP BY is complete. (CVS 702)
FossilOrigin-Name: 18745c67acdf7ebec378f5538174117970e9f5cc
and continued by another. Leave in the documentation the warning about not
carrying a database connection across fork() but do not test for it any more.
Ticket #130. (CVS 701)
FossilOrigin-Name: bdbdb866f2e76abd1f8f545adadc9a900ed0cd1a
and reopening the database. Also fixed an unrelated bug in the version
2.6.0 database format upgrade logic. The upgrade logic bug was found while
testing the trigger fixes. (CVS 697)
FossilOrigin-Name: 04973fc2a6a0c93877de7e564618e0e9fcffc06c
a table while the "count_changes" pragma is turned on. Up the version number
to 2.6.1. (CVS 690)
FossilOrigin-Name: 612df004017b241651074ee859096dd0ee5062b8
tests for automatic upgrade and for failing if reading a more advanced version
of the database. Ticket #107. (CVS 682)
FossilOrigin-Name: 0493e39c1cbbe4a38e990a2370181a79606af222
to fail when using an index on a column containing an empty string. This
fix is an incompatible file-format change. (CVS 681)
FossilOrigin-Name: 20d152fcddb4fa53556a9c93c7a869600a7c5183
indexed tables when there is a subquery in the WHERE clause. Add tests
to verify correct operation. (CVS 680)
FossilOrigin-Name: bbca16f88d00cd33ac7229edf3ee4623eff6e62f
SHOW_DATATYPES pragma is ON. Eliminate the NULL pointer that used to separate
the beginning of datatypes from the end of column names so that the callback
can test to see whether or not datatypes are provided. This is an
incompatible changes, but since the prior behavior was never documented, we
will let it in. (CVS 670)
FossilOrigin-Name: b98727246d5fcc1b097b577be498a77e954c5dc4
as it appears in the CREATE TABLE statement, if available. Also: removed
the ".reindex" command from the shell. (CVS 669)
FossilOrigin-Name: ff8b6f4ee8099a7170cb786b8ead9a3e42ab5869
pages close to related pages in order to keep data structures near each other
in the database file. This improves access speed in some circumstances. (CVS 667)
FossilOrigin-Name: fd7e41f0eed80fb1c7e18eb84834ec3cea74a649
