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
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
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
default. Specify an alternative limit using an argument to the pragma.
Ticket #2176. (CVS 3609)
FossilOrigin-Name: d564a039f27be2bb2c3973e79dc99b25869139da
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
schema symbol table. Ticket #2156. This change also includes some debugging
enhancements. (CVS 3578)
FossilOrigin-Name: 43fe7fc1c38f8d9b3c1346cb1d890c2e25cefe15
Identify all tests where we deliberately derefence freed memory by adding
a "-misuse" tag. (CVS 3550)
FossilOrigin-Name: 70a862702d6dfcfe73bdeef8f0502c6c50e32a3a
if missing. Pager is more careful to clear its file size cache. Remove
an assert() in VDBE that might fail on a corrupt database file. (CVS 3547)
FossilOrigin-Name: bf1afd016ad71dac90e58540122108f92e77ce3d
that contain the rowid or which use indices that contain the rowid.
Ticket #2116. (CVS 3536)
FossilOrigin-Name: f245f5c2c2d337fe6458824beb7f9e721837765f
to be reordered with A and B. This used to be the case but the capability
was removed by (3203) and (3052) in response to ticket #1652. This change
restores the capability. (CVS 3529)
FossilOrigin-Name: 7393c81b8cb9d4344ae744de9eabcb3af64f1db8
prior to fts2.c r1.10 meant that such large terms caused an eventual
stack overflow. (CVS 3523)
FossilOrigin-Name: 66581162daa188d23078c9d21fd5b2563d4d238a
