Overview
| Comment: | :-) (CVS 202) |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: | 04530e451662e298506d314ce014a2643f4ff813 |
| User & Date: | drh 2001-04-05 16:25:53 |
Context
|
2001-04-05
| ||
| 16:49 | :-) (CVS 203) check-in: b5f994fe user: drh tags: trunk | |
| 16:25 | :-) (CVS 202) check-in: 04530e45 user: drh tags: trunk | |
| 15:57 | i18n changes (CVS 201) check-in: 8390f652 user: drh tags: trunk | |
Changes
Changes to www/c_interface.tcl.
1 2 3 4 5 6 7 8 9 10 11 .. 73 74 75 76 77 78 79 80 81 82 83 84 85 86 ... 372 373 374 375 376 377 378 379 380 381 382 383 384 385 |
#
# Run this Tcl script to generate the sqlite.html file.
#
set rcsid {$Id: c_interface.tcl,v 1.13 2000/11/28 20:46:39 drh Exp $}
puts {<html>
<head>
<title>The C language interface to the SQLite library</title>
</head>
<body bgcolor=white>
<h1 align=center>
................................................................................
int sqlite_complete(const char *sql);
void sqlite_busy_handler(sqlite*, int (*)(void*,const char*,int), void*);
void sqlite_busy_timeout(sqlite*, int ms);
const char sqlite_version[];
int sqlite_exec_printf(
sqlite*,
char *sql,
int (*)(void*,int,char**,char**),
void*,
char **errmsg,
................................................................................
<p>The SQLite library exports the string constant named
<b>sqlite_version</b> which contains the version number of the
library. The header file contains a macro SQLITE_VERSION
with the same information. If desired, a program can compare
the SQLITE_VERSION macro against the <b>sqlite_version</b>
string constant to verify that the version number of the
header file and the library match.</p>
<h2>Changing the libraries response to locked files</h2>
<p>The GDBM library supports database locks at the file level.
If a GDBM database file is opened for reading, then that same
file cannot be reopened for writing until all readers have closed
the file. If a GDBM file is open for writing, then the file cannot
|
| > > > > > > > > > > > > > > > > > > > |
1 2 3 4 5 6 7 8 9 10 11 .. 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 ... 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 |
#
# Run this Tcl script to generate the sqlite.html file.
#
set rcsid {$Id: c_interface.tcl,v 1.14 2001/04/05 16:25:53 drh Exp $}
puts {<html>
<head>
<title>The C language interface to the SQLite library</title>
</head>
<body bgcolor=white>
<h1 align=center>
................................................................................
int sqlite_complete(const char *sql);
void sqlite_busy_handler(sqlite*, int (*)(void*,const char*,int), void*);
void sqlite_busy_timeout(sqlite*, int ms);
const char sqlite_version[];
const char sqlite_encoding[];
int sqlite_exec_printf(
sqlite*,
char *sql,
int (*)(void*,int,char**,char**),
void*,
char **errmsg,
................................................................................
<p>The SQLite library exports the string constant named
<b>sqlite_version</b> which contains the version number of the
library. The header file contains a macro SQLITE_VERSION
with the same information. If desired, a program can compare
the SQLITE_VERSION macro against the <b>sqlite_version</b>
string constant to verify that the version number of the
header file and the library match.</p>
<h2>Library character encoding</h2>
<p>By default, SQLite assumes that all data uses a fixed-size
8-bit character (iso8859). But if you give the --enable-utf8 option
to the configure script, then the library assumes UTF-8 variable
sized characters. This makes a difference for the LIKE and GLOB
operators and the LENGTH() and SUBSTR() functions. The static
string <b>sqlite_encoding</b> will be set to either "UTF-8" or
"iso8859" to indicate how the library was compiled. In addition,
the <b>sqlite.h</b> header file will define one of the
macros <b>SQLITE_UTF8</b> or <b>SQLITE_ISO8859</b>, as appropriate.</p>
<p>Note that the character encoding mechanism used by SQLite cannot
be changed at run-time. This is a compile-time option only. The
<b>sqlite_encoding</b> character string just tells you how the library
was compiled.</p>
<h2>Changing the libraries response to locked files</h2>
<p>The GDBM library supports database locks at the file level.
If a GDBM database file is opened for reading, then that same
file cannot be reopened for writing until all readers have closed
the file. If a GDBM file is open for writing, then the file cannot
|
Changes to www/changes.tcl.
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 |
proc chng {date desc} {
puts "<DT><B>$date</B></DT>"
puts "<DD><P><UL>$desc</UL></P></DD>"
}
chng {2001 Apr 5 (1.0.29)} {
<li>The LIKE and GLOB operators now assume both operands are
UTF-8 strings if the library is configured with the "--enable-utf8"
option. If not configured for UTF-8 but using a version of TCL
that supports UTF-8, then a conversion from UTF-8 to iso8859 and
back again is done inside the TCL interface.</li>
}
chng {2001 Apr 4 (1.0.28)} {
<li>Added limited support for transactions. At this point, transactions
will do table locking on the GDBM backend. There is no support (yet)
for rollback or atomic commit.</li>
|
> > > | < | > | |
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 |
proc chng {date desc} {
puts "<DT><B>$date</B></DT>"
puts "<DD><P><UL>$desc</UL></P></DD>"
}
chng {2001 Apr 5 (1.0.29)} {
<li>The library now assumes data is stored as UTF-8 if the --enable-utf8
option is given to configure. The default behavior is to assume
iso8859-x, as it has always done. This only makes a difference for
LIKE and GLOB operators and the LENGTH and SUBSTR functions.</li>
<li>If the library is not configured for UTF-8 and the Tcl library
is one of the newer ones that uses UTF-8 internally,
then a conversion from UTF-8 to iso8859 and
back again is done inside the TCL interface.</li>
}
chng {2001 Apr 4 (1.0.28)} {
<li>Added limited support for transactions. At this point, transactions
will do table locking on the GDBM backend. There is no support (yet)
for rollback or atomic commit.</li>
|