names in sqlite3_exec() until there is a need to use the array. In
the common case where there is no callback, this avoids a malloc() call. (CVS 4905)
FossilOrigin-Name: d8686abcdf9e566571033f2f137142f742df9357
I have not even attempted to compile so I am certain there are
countless errors. (CVS 4231)
FossilOrigin-Name: deb7ecd65f7b83eaf0ba610eeef3b0ede61db1c3
misused. But getting rid of them removes a library dependency. And
it avoids warnings from the OpenBSD compiler. Ticket #2336. (CVS 3916)
FossilOrigin-Name: ba4845b32bdf38e623c4f7246e6e327715bbba4b
carried in the higher bits of the integer return codes. This must be
enabled using the sqlite3_extended_result_code() API. Only a few extra
result codes are currently defined. (CVS 3422)
FossilOrigin-Name: ba579ddc4361fc6e8ea66f9385770d70dfe94751
memory allocator. Convert sqlite3_free() and sqlite3_mprintf() to also
use the OS-layer memory allocator. (CVS 3298)
FossilOrigin-Name: 85a66a25e97471d3c459c8da6a96990b0537dc7d
http://scan.coverity.com/ Found 1 potential segfault in sqlite3_mprintf().
Also 2 failures to fclose() following a malloc() failure. And lots of
cases where unnecessary conditionals could be removed from the code. (CVS 3126)
FossilOrigin-Name: e510e6dd9d6261f33b853af3b32d155b9d6b63b3
being used. Ticket #1601. Also implemented the suggestion of
ticket #1603. Memory management is now off by default at compile-time.
The sqlite3_enable_memory_management() API has been removed. (CVS 2919)
FossilOrigin-Name: 5d9c6aa964305c3f36741ff0058da5b5f3ce0d24
connection now *must* be called "sqlite3". You cannot call it "sqlite".
This might break existing code. (CVS 1941)
FossilOrigin-Name: 3ddf5a9d1c480a2e3aa32685879063b11afddbe1
