diff --git a/manifest b/manifest index d503280a3d..b829f505c1 100644 --- a/manifest +++ b/manifest @@ -1,5 +1,5 @@ -C Makefile\schanges\sfor\sbuilding\swindows\sDLLs.\s(CVS\s1517) -D 2004-06-01T01:45:11 +C Fix\stypos\sin\sversion\s3\sdocuments.\s(CVS\s1518) +D 2004-06-01T10:01:25 F Makefile.in ab7b0d5118e2da97bac66be8684a1034e3500f5a F Makefile.linux-gcc b86a99c493a5bfb402d1d9178dcdc4bd4b32f906 F README f1de682fbbd94899d50aca13d387d1b3fd3be2dd @@ -185,7 +185,7 @@ F www/arch2.fig 613b5ac63511109064c2f93c5754ee662219937d F www/arch2.gif 49c6bb36160f03ca2b89eaa5bfb1f560c7d68ee7 F www/audit.tcl 90e09d580f79c7efec0c7d6f447b7ec5c2dce5c0 F www/c_interface.tcl 2176519fc2bd2d2cf6fe74fd806fc2d8362de2c8 -F www/capi3.tcl 2825f418f5c5d8376d0e83474796363db1d9e875 +F www/capi3.tcl a940c5ca0b0ebafd5acfe2ceca5a388bd8cfb468 F www/capi3ref.tcl 4248a45a0fd21fe0c116326300408d0999a028b5 F www/changes.tcl 9d562205db584d26b358ebe93fb58039feefd1b8 F www/common.tcl f786e6be86fb2627ceb30e770e9efa83b9c67a3a @@ -193,7 +193,7 @@ F www/conflict.tcl fb8a2ba83746c7fdfd9e52fa7f6aaf5c422b8246 F www/copyright-release.html 294e011760c439c44951a6bfecd4c81a1ae359e8 F www/copyright-release.pdf cfca3558fc97095e57c6117d08f1f5b80d95125a F www/copyright.tcl 82c9670c7ddb0311912ab7fe24703f33c531066c -F www/datatype3.tcl ddfc758410109cb6a9bd617836b9334a7ddbd929 +F www/datatype3.tcl 22f59662aa4b7a246ef56ee1bf40c514fc06e21c F www/datatypes.tcl 566004b81c36877397ddbe6e1907aae6065f6b41 F www/docs.tcl 0dcbf954907bd5dbfb7f1e0220f4e50516e07cd3 F www/download.tcl 8c84f15695c92cb01486930055fdf5192995f474 @@ -214,7 +214,7 @@ F www/support.tcl 67682848d6ddd283370451dc3da2e56cded9fc9a F www/tclsqlite.tcl 19191cf2a1010eaeff74c51d83fd5f5a4d899075 F www/vdbe.tcl 59288db1ac5c0616296b26dce071c36cb611dfe9 F www/whentouse.tcl a8335bce47cc2fddb07f19052cb0cb4d9129a8e4 -P 89f54f1ffdddc99340777cda6d9b1d7446549fa2 -R cdfbb65facdbc30feb7d845fb9129454 +P 11c5d6ab39d04e05a3a1b68477f159b17311a6da +R 027b458639fb8210c23c1409b741ebc9 U drh -Z c2c1d678f12db45dfa44d1a3efee9c99 +Z ebfcd1866cc601ad5bc0d08d518b3a6a diff --git a/manifest.uuid b/manifest.uuid index b01da5a52d..5ad148f136 100644 --- a/manifest.uuid +++ b/manifest.uuid @@ -1 +1 @@ -11c5d6ab39d04e05a3a1b68477f159b17311a6da \ No newline at end of file +915cba57123f859c7f128bd52580573877c502ba \ No newline at end of file diff --git a/www/capi3.tcl b/www/capi3.tcl index 4a6546af50..994417b3d3 100644 --- a/www/capi3.tcl +++ b/www/capi3.tcl @@ -1,4 +1,4 @@ -set rcsid {$Id: capi3.tcl,v 1.2 2004/05/31 18:51:59 drh Exp $} +set rcsid {$Id: capi3.tcl,v 1.3 2004/06/01 10:01:25 drh Exp $} source common.tcl header {C/C++ Interface For SQLite Version 3} puts { @@ -378,7 +378,7 @@ The sqlite3_create_collation() function specifies a collating sequence name and a comparison function to implement that collating sequence. The comparison function is only used for comparing text values. The eTextRep parameter is one of SQLITE3_UTF8, SQLITE3_UTF16LE, SQLITE3_UTF16BE, or -SQLITE3_ANY to specify which text representation to comparison function works +SQLITE3_ANY to specify which text representation the comparison function works with. Separate comparison functions can exist for the same collating sequence for each of the UTF-8, UTF-16LE and UTF-16BE text representations. The sqlite3_create_collation16() works like sqlite3_create_collation() except diff --git a/www/datatype3.tcl b/www/datatype3.tcl index 260f5064fb..ab3022ba73 100644 --- a/www/datatype3.tcl +++ b/www/datatype3.tcl @@ -1,4 +1,4 @@ -set rcsid {$Id: datatype3.tcl,v 1.2 2004/05/31 18:51:59 drh Exp $} +set rcsid {$Id: datatype3.tcl,v 1.3 2004/06/01 10:01:25 drh Exp $} source common.tcl header {Datatypes In SQLite Version 3} puts { @@ -61,10 +61,10 @@ result of an expression at compile time.

In SQLite version 3, the type of a value is associated with the value itself, not with the column or variable in which the value is stored. (This is sometimes called - + manifest typing.) All other SQL databases engines that we are aware of use the more -restrict system of static typing where the type is associated with +restrictive system of static typing where the type is associated with the container, not the value.

@@ -82,10 +82,10 @@ a column is called its "affinity".

Each column in an SQLite 3 database is assigned one of the following type affinities:

A column with TEXT affinity stores all data using storage classes @@ -125,10 +125,9 @@ of the column, according to the following rules:

  • If the datatype for a column contains the string "BLOB" or if - not datatype is specified then the column has affinity NONE.

    + no datatype is specified then the column has affinity NONE.

    -
  • Otherwise, the affinity is NUMERIC. Notice that a column - where no datatype is specified is given affinity NUMERIC.

    +
  • Otherwise, the affinity is NUMERIC.

    If a table is created using a "CREATE TABLE <table> AS @@ -183,7 +182,7 @@ two values being compared, according to the following rules:

    SQLite may attempt to convert values between the numeric storage classes (INTEGER and REAL) and TEXT before performing a comparison. For binary comparisons, this is done in the cases enumerated below. -The term “expression” used in the bullet points below means any +The term "expression" used in the bullet points below means any SQL scalar expression or literal other than a column value.