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
in support of the integrity_check enhancement of check-in (3609)
and ticket #2176. (CVS 3610)
FossilOrigin-Name: ab6322bf9398c2989b648b24c1ebdf09493accdf
default. Specify an alternative limit using an argument to the pragma.
Ticket #2176. (CVS 3609)
FossilOrigin-Name: d564a039f27be2bb2c3973e79dc99b25869139da
The code is normally omitted. You must compile with -DSQLITE_TEST
or -DSQLITE_DEBUG to enable it. (CVS 3606)
FossilOrigin-Name: 1b26d6875612a0ed25d6e293f005ea4966692759
Calling UPDATE against an fts table in a UTF-16 database inserts
corrupted data into the database. The UTF-8 data is being inserted
directly. This appears to happen because sqlite3_ value_text()
destructively coerces a value to UTF-8, and it's never converted back
when updating the table. This works around the problem by rearranging
things so that the update happens before the coercion. (CVS 3596)
FossilOrigin-Name: 4f2ab4b6320ffc621900049b41f50bc30d76d7f5
handles a LEFT JOIN where the a term from the right table of the join uses
an IS NULL constraint. Ticket #2177. This check-in also adds the new test
cases that were suppose to have been added with (3494) but which were
mistakenly omitted. (CVS 3595)
FossilOrigin-Name: 335863e4d16113fb9ecebce35d2db043771d98b1
Ticket #2172. Note this problem only comes up with certain grammars,
and does not impact SQLite. On the other hand, it might cause SQLite
to run slower. So we might want to revisit this change at some point. (CVS 3594)
FossilOrigin-Name: d537aa5edecb5c7b84d8eb876453f385f6f3d91a
unreachable. The changes does not effect the code that is generated for
the SQLite parser. Ticket #2164. (CVS 3591)
FossilOrigin-Name: f4ee5d83e177e7ed9f180454c01d46a395a5715d
drh