SQLite

Check-in [2812dd5fc9]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Bump the version number for the next release. (CVS 1176)
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 2812dd5fc99c959f41b24b0f6b280b67b06fe9d9
User & Date: drh 2004-01-14 13:43:43.000
Context
2004-01-14
13:50
Version 2.8.11 (CVS 1177) (check-in: a9f25347de user: drh tags: trunk)
13:43
Bump the version number for the next release. (CVS 1176) (check-in: 2812dd5fc9 user: drh tags: trunk)
13:38
Ignore NULLs in a subquery as the right operand of IN. Ticket #565. (CVS 1175) (check-in: c9e7996fb9 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to VERSION. 
1

2.8.10

|

1

2.8.11
Changes to www/changes.tcl.
︙︙
21
22
23
24
25
26
27
28





29
30
31
32
33
34
35



proc chng {date desc} {
  puts "<DT><B>$date</B></DT>"
  puts "<DD><P><UL>$desc</UL></P></DD>"
}

chng {2004 January 14 (2.8.10)} {





<li>Fix a potential database corruption problem on Unix caused by the fact
    that all posix advisory locks are cleared whenever you close() a file.
    The work around it to embargo all close() calls while locks are 
    outstanding.</li>
<li>Performance enhancements on some corner cases of COUNT(*).</li>
<li>Make sure the in-memory backend response sanely if malloc() fails.</li>
<li>Allow sqlite_exec() to be called from within user-defined SQL








|
>
>
>
>
>








21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40



proc chng {date desc} {
  puts "<DT><B>$date</B></DT>"
  puts "<DD><P><UL>$desc</UL></P></DD>"
}

chng {2004 January 14 (2.8.11)} {
<li>Fix a bug in how the IN operator handles NULLs in subqueries.  The bug
    was introduced by the previous release.</li>
}

chng {2004 January 13 (2.8.10)} {
<li>Fix a potential database corruption problem on Unix caused by the fact
    that all posix advisory locks are cleared whenever you close() a file.
    The work around it to embargo all close() calls while locks are 
    outstanding.</li>
<li>Performance enhancements on some corner cases of COUNT(*).</li>
<li>Make sure the in-memory backend response sanely if malloc() fails.</li>
<li>Allow sqlite_exec() to be called from within user-defined SQL
︙︙