with the freelist. (1) Avoid journaling pages of a table that is being
deleted. (2) Do not read the original content of pages being pulled off
of the freelist. (CVS 3671)
FossilOrigin-Name: 2ba5be311945a4c15b6dce7c01efefb513b9a973
interface is likely to change and may be completely abandoned in the
near future. (CVS 3665)
FossilOrigin-Name: 007ca283892a66dd8b9e0dfece4f75d0d08a4300
a REAL table column by GROUP BY. Ticket #2251. Also make sure default
values are correctly expanded. There may be other places in the code
where this issue comes up - we need to look further. (CVS 3659)
FossilOrigin-Name: e11bbf174c5a2fa75e3d1dd450c8b2a18f40e4da
affinity coercions. Ticket #2249. Additional cleanup and testing
of the OR optimization. (CVS 3658)
FossilOrigin-Name: 908daaa9ab86e0bd1da6d0807d6aaba240c3cee0
Fix the comparison operators when both sides of an IN operator are
expressions (ticket #2248).
Changes to main.mk for adding FTS2 into the standard build also
got mixed in with this check-in by mistake. (CVS 3656)
FossilOrigin-Name: da81725ca1cd894b3f2d734767e10cc0dc329566
change uses of (open ... a) to (open ... RDWR) to work around
inconsistencies in behavior across various platforms. (CVS 3645)
FossilOrigin-Name: 50e86b0368ae0268e7f07e44a746e13ad86a3b8b
huge VDBE programs resulting from deeply nested triggers. This is an
interim fix until we rework triggers to use subroutines. (CVS 3640)
FossilOrigin-Name: 22769e2d37f4912ad388d2ed79f93571d0279fb8
backwards compatible since SQLite has not previously supported
explicit collations. Need to add tests of this new behavior. (CVS 3633)
FossilOrigin-Name: 3638823a629164e4158f76d03ff2cea1eab34e9d
of the VM rather than the stack, to avoid problems with leftovers on the
stack interfering with other operations. Ticket #2217. (CVS 3632)
FossilOrigin-Name: 2bd4b62a20219f939ac2ac22440dc7fc0449f766
When creating fts tables in an attached database, the backing tables
are created in database 'main'. This change propagates the
appropriate database name to the routines which build sql statements.
Note that I propagate the database name and table name separately. I
briefly considered just making the table name be "db.table", but it
didn't fit so well in the model used to store the table name and other
information, and having the db name passed separately seemed a bit
more transparent. (CVS 3631)
FossilOrigin-Name: 283385d20724f0144f38de89bd179715ee5e738b
sure unused terms to the right in the ORDER BY clause to not reference other
tables in a join. Ticket #2211. Additional test cases needed before
closing this ticket. (CVS 3629)
FossilOrigin-Name: 912faf18d86416b1a36660851f8a4554e6746875
until 3.4.0, since we'll likely end up with some minor technical
imcompatibilities. (CVS 3626)
FossilOrigin-Name: 9740aa95a3f848fc663c88263a911fbc76ada243
the quick set does) and a few new tests have been added. But many more
tests are needed. Rules for combining collations need to be worked out. (CVS 3624)
FossilOrigin-Name: 85cca7cd252d46ba71d302a89bc67c56146ec552
