mirrors/sqlite
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
5,351 Commits 1,487 Branches 166 Tags 416 MiB
01859b0b07
Commit Graph

14 Commits

Author SHA1 Message Date
danielk1977
01874bfc51 Adjust the test suite to account for recent changes related to #2822. Most changes are related to English language error messages only. (CVS 4622) 
FossilOrigin-Name: 2f88b9b3e3c9abc3ae4a5dcef82707dd74f8aace
 2007-12-13 07:58:50 +00:00
drh
1e281291fb ORDER BY in a compound SELECT will first match against the left-most SELECT. 
If there is no match there, it begins working its way to the right. (CVS 4621)

FossilOrigin-Name: 56063ec84b130bcdb0e90bc76fabca394d0d867f
 2007-12-13 03:45:07 +00:00
drh
9a99334d54 Towards getting ORDER BY to match against the correctin columns. 
This version only looks at the left-most column in a compound SELECT.
That is the correct thing to do, but not what SQLite has historically done. (CVS 4620)

FossilOrigin-Name: bbddf16ac9539c7d48adfc73c5a90eecb8df6865
 2007-12-13 02:45:31 +00:00
danielk1977
3bdca9c9a5 Test suite fixes for builds that define OMIT symbols. (CVS 2962) 
FossilOrigin-Name: 3a54a33dcb7e765ee3773397407e8929a8cfe1a9
 2006-01-17 09:35:01 +00:00
drh
a97fdd3bfc Add support for the TOTAL() aggregate function - works like SUM() except 
that it returns 0 instead of NULL when presented with an empty list. (CVS 2930)

FossilOrigin-Name: a7f528ff3446d50b280fb0b85063879e3ac5751a
 2006-01-12 22:17:50 +00:00
drh
3d1d95e625 The SUM() aggregate function returns an integer result if all inputs are 
integers.  Any single non-integer input causes the result to be a floating
point value. (CVS 2669)

FossilOrigin-Name: 21adf4bd99e732650a1e8e9a1cc954126983a654
 2005-09-08 10:37:01 +00:00
danielk1977
3e8c37e7f8 Modify test scripts to work when SQLITE_OMIT_SUBQUERY (along with other OMIT macros) is defined. (CVS 2251) 
FossilOrigin-Name: bb0254ab14417f0ab40f10f37cb63a60507f070a
 2005-01-21 03:12:14 +00:00
danielk1977
27c774388a Ensure tests pass when SQLITE_OMIT_COMPOUND_SELECT is defined. (CVS 2138) 
FossilOrigin-Name: 007be591b7829f9ff38e4b14ba5a5043796c2ff3
 2004-11-22 13:35:41 +00:00
drh
92febd92ad Tcl interface transfers values directly between SQLite and Tcl_Objs, without 
at translation to strings. (CVS 1898)

FossilOrigin-Name: e97c331362545ce21117776c7b61d3488668f2bf
 2004-08-20 18:34:20 +00:00
drh
9eb516c0eb min() ignores NULL values. Ticket #800. (CVS 1802) 
FossilOrigin-Name: 166234a2b61e1d6a501e48dde1caec0a02bec90b
 2004-07-18 20:52:32 +00:00
danielk1977
3aeab9e438 Apply (1679) to version 3. Ticket #777. (CVS 1680) 
FossilOrigin-Name: 0a26b9158095f0995fce2f0ccdfb383ab26c76a5
 2004-06-24 00:20:04 +00:00
drh
562528c480 Do all WHERE clauses tests, even if an index is used for lookup so that 
we know the test cannot be FALSE.  The test might end up being NULL in which
case it would need to be treated as false.  Ticket #461. (CVS 1103)

FossilOrigin-Name: 5aea81488b2d3bcdc009ccf0f0ffcda046e38d79
 2003-09-27 00:41:27 +00:00
drh
1288c9561d Multiplying NULL by zero gives NULL, not zero. I misread the test data 
and coded it wrong.  This check-in fixes the problem. (CVS 601)

FossilOrigin-Name: df9cc852ad02dbec5558d3915a0303f7e7b79b2b
 2002-06-01 21:41:10 +00:00
drh
f570f011eb Refinements to NULL processing: NULLs are indistinct for DISTINCT and UNION. 
Multiplying a NULL by zero yields zero. In a CASE expression, a NULL comparison
is considered false, not NULL.  With these changes, NULLs in SQLite now work
the same as in PostgreSQL and in Oracle. (CVS 600)

FossilOrigin-Name: da61aa1d238539dff9c43fd9f464d311e28d669f
 2002-05-31 15:51:25 +00:00