actually tries to write data into a readonly file. It is OK to start a
transaction on a read-only file, and doing so will get you a read lock. This
change allows TEMP tables to be read/write even though the main database is
readonly. (CVS 607)
FossilOrigin-Name: 9ef795d1d756a404d2123ebc19df1985b19c9888
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
duration of a transaction, rather than closing it and reopening it
for each statement. (Ticket #53) (CVS 599)
FossilOrigin-Name: 7a24336d50e72006b2cc0e4feb292b946e79d5f3
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
so that they will appear together with the other List opcodes in the
documentation. (CVS 583)
FossilOrigin-Name: c53b0b9283c5c34def87d58b03fd979d03dc0890
a memory leak. I'm not sure if the memory leak was pre-existing or a result
of this change. (CVS 581)
FossilOrigin-Name: 4d27ee411902a197cd72416ca9da9197d3f87f13
quotes and not double quotes for quoting literal strings. This is for
portability to other databases that only support single quote string literals. (CVS 574)
FossilOrigin-Name: f795afd63f19ab61c2b3b96621cb6dda31ce0379
the same time and return an SQLITE_MISUSE error. Also return this error
if an attempt is made to use a closed database. (CVS 558)
FossilOrigin-Name: a05fabd2df1cb38c555a7b2f31b0ca687db500c2
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
can be used to encode binary data for use in INSERT and UPDATE statements.
This is just an initial checking. The code has not yet been integrated into
the library. (CVS 545)
FossilOrigin-Name: 57f7c59713299b03b10ba9c1a5883e2c08a8b138
