multiple database files. Many regession tests pass - but not all of them.
Do not use this version except for debugging SQLite itself. (CVS 883)
FossilOrigin-Name: d2fb2bb50cf1e13feb90995079f291384abd6ba9
side-efffect, allow the GROUP BY clause to refer to columns by their integer
column number. Ticket #237. (CVS 856)
FossilOrigin-Name: 187d9c405891e543fc706f8ddb41f3966a842214
to make cursor numbers right on nested subqueries. Also added OP_Gosub and
OP_Return but have not actually used them for anything yet. (CVS 727)
FossilOrigin-Name: c602603e7cd8dc5c8bb9db2748eacab650de5bf0
use an index for sorting. It has to sort as a separate operation after
the GROUP BY is complete. (CVS 702)
FossilOrigin-Name: 18745c67acdf7ebec378f5538174117970e9f5cc
to fail when using an index on a column containing an empty string. This
fix is an incompatible file-format change. (CVS 681)
FossilOrigin-Name: 20d152fcddb4fa53556a9c93c7a869600a7c5183
SHOW_DATATYPES pragma is ON. Eliminate the NULL pointer that used to separate
the beginning of datatypes from the end of column names so that the callback
can test to see whether or not datatypes are provided. This is an
incompatible changes, but since the prior behavior was never documented, we
will let it in. (CVS 670)
FossilOrigin-Name: b98727246d5fcc1b097b577be498a77e954c5dc4
as it appears in the CREATE TABLE statement, if available. Also: removed
the ".reindex" command from the shell. (CVS 669)
FossilOrigin-Name: ff8b6f4ee8099a7170cb786b8ead9a3e42ab5869
for the right-hand table not matching the left table occurred after all
ON, USING, WHERE clause processing. The test should occur after ON and
USING clauses are checked but before the WHERE clause is check. This fix
works as long as the total number of "AND" separated terms in the ON, USING,
and WHERE clause does not exceed 32. To do: make this work for any number
of terms and add test cases.
that (CVS 639)
FossilOrigin-Name: 8b6574cfa86daaae910f8f3ee3c4723a21fb9e53
This passes all regression tests, but more testing is needed to exercise
all paths through the new code. (CVS 631)
FossilOrigin-Name: 43c5aff5d078bce9292683cd40311e0dcc81ac14
in the parser to make the parse tables much smaller. This reduced the size
of the library by 15K. (CVS 605)
FossilOrigin-Name: 7ac5bd293cbb2bf252f31f1571f7efac7e77280a
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
to discard the query results. Such selects are intended to be used to call
user-defined functions for their side-effects. They do not return results. (CVS 594)
FossilOrigin-Name: f8041f3d4d3350b4086cd6ba3e9006bdde8546a9
Operations on a NULL value yield a NULL result. This change makes SQLite
operate more like the SQL spec, but it may break existing applications that
assumed the old behavior. All the old tests pass but we still need to add
new tests to better verify the new behavior. Fix for ticket #44. (CVS 589)
FossilOrigin-Name: 9051173742f1b0e15a809d12a0c9c98fd2c4614d
syntax. The basic functionality is there but there is still a lot of testing
to do. (CVS 587)
FossilOrigin-Name: 99bd1f5b9a1a20bfeefe15c00d96a34a5f40923e
We now recognize all kinds of joins, but we don't actually do anything with
them yet. (CVS 586)
FossilOrigin-Name: e238643efdbe1394c7ff85e34e486f7c6082b6cc
represent a FROM clause and IdList is used for everything else. This change
allows SrcList to grow to support outer joins without burdening the other
uses of IdList. (CVS 584)
FossilOrigin-Name: a167b71d8c27e870bc3079c6132e483bffc83298
doing the flattening optimization or evaluating subqueries. Otherwise, the
result set column names are generated incorrectly or after they are needed. (CVS 553)
FossilOrigin-Name: 08f27cb36805d38648274b6fe91dec43a5910057
subselect does not contain a FROM clause. Handle the special case where
a WHERE clause is constant. (CVS 548)
FossilOrigin-Name: 24e4cf73d22bb41d26bf3c833f1854a9c90923e8
care not to generate column name headers if the output is an intermediate table.
Otherwise the column headers are not generated correctly if a compound SELECT
statement appears as an expression in part of the WHERE clause. (CVS 543)
FossilOrigin-Name: a06d9acdd5af0dc69b3a4d024de082631254aead
