Index: www/c_interface.tcl ================================================================== --- www/c_interface.tcl +++ www/c_interface.tcl @@ -1,9 +1,9 @@ # # Run this Tcl script to generate the sqlite.html file. # -set rcsid {$Id: c_interface.tcl,v 1.40 2004/05/31 15:06:29 drh Exp $} +set rcsid {$Id: c_interface.tcl,v 1.41 2004/08/30 14:58:12 drh Exp $} source common.tcl header {The C language interface to the SQLite library} puts {

The C language interface to the SQLite library

@@ -693,11 +693,11 @@ result.

As an example, consider the following query:

-SELECT employee_name, login, host FROM users WHERE logic LIKE 'd%'; +SELECT employee_name, login, host FROM users WHERE login LIKE 'd%';

This query will return the name, login and host computer name for every employee whose login begins with the letter "d". If this query is submitted to sqlite_get_table the result might Index: www/nulls.tcl ================================================================== --- www/nulls.tcl +++ www/nulls.tcl @@ -1,9 +1,9 @@ # # Run this script to generated a nulls.html output file # -set rcsid {$Id: nulls.tcl,v 1.6 2004/05/31 15:06:30 drh Exp $} +set rcsid {$Id: nulls.tcl,v 1.7 2004/08/30 14:58:12 drh Exp $} source common.tcl header {NULL Handling in SQLite} puts {

NULL Handling in SQLite Versus Other Database Engines

@@ -105,11 +105,11 @@ nulls are distinct in a UNIQUE column Yes Yes Yes No -Yes +(Note 4) No Yes nulls are distinct in SELECT DISTINCT No @@ -237,11 +237,11 @@ 3.  MySQL version 3.23.41 does not support UNION. 4.  -SQL Anywhere and Borland Interbase +DB2, SQL Anywhere, and Borland Interbase do not allow NULLs in a UNIQUE column. 5.  Borland Interbase does not support CASE expressions.