some other parts of the SQL engine do not, which can lead to some strange
results. (CVS 1368)
FossilOrigin-Name: 9f2b6d9d3a07e25fcdb7e8290da7a182a65c37b2
This passes all regression tests, but more testing is needed to exercise
all paths through the new code. (CVS 631)
FossilOrigin-Name: 43c5aff5d078bce9292683cd40311e0dcc81ac14
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
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
We now recognize all kinds of joins, but we don't actually do anything with
them yet. (CVS 586)
FossilOrigin-Name: e238643efdbe1394c7ff85e34e486f7c6082b6cc
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
