Commit Graph

7 Commits

Author SHA1 Message Date
drh c01b7306ae Make sure the ORDER BY collating sequences are compatible with the
comparison collations before using the merge algorithm for compound
SELECT statements.  Candidate fix for ticket [6709574d2a8d8].

FossilOrigin-Name: fc3630cdef6e2cdbfb4e7b373d1a094753e55016
2013-05-07 17:49:08 +00:00
drh 74073b6da8 Add test cases to verify that ticket #3314 has been fixed. (CVS 5579)
FossilOrigin-Name: b46267ff07f9b967bb7aee16b6d9dd8d0bd23f0c
2008-08-21 14:24:29 +00:00
danielk1977 de3e41e304 Fix (make test) with SQLITE_OMIT_COMPOUND_SELECT. Ticket #3235. (CVS 5530)
FossilOrigin-Name: 9ca975c8fdeaae7d5af8fe62e097d8d251362cfe
2008-08-04 03:51:24 +00:00
drh 85e9e22b33 Increased test coverage. (CVS 5414)
FossilOrigin-Name: 7cf91e08c08ce515c24c738c7d079f5b81eebee6
2008-07-15 00:27:34 +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
drh ff354e91ba If a unique index covers any prefix of the ORDER BY clause then let it
satisfy the ORDER BY clause. (CVS 5301)

FossilOrigin-Name: e53403b6d742be83c5b130ed6cef4035d081d613
2008-06-25 02:47:57 +00:00
drh fae37af17f Add new test script for compound select statements. (CVS 5300)
FossilOrigin-Name: a193b1612e7ccd1c8f6136ece8d4768fccfe43fe
2008-06-25 02:22:32 +00:00