Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix to the documentation on sqlite3_create_function. Ticket #899. (CVS 2128) |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
4ab1d012f0f365c46bcabe67eace891e |
| User & Date: | drh 2004-11-20 21:02:14 |
Context
|
2004-11-21
| ||
| 01:02 | AUTOINCREMENT documentation added. Improvements to lang.html. (CVS 2129) check-in: ac72a1d5 user: drh tags: trunk | |
|
2004-11-20
| ||
| 21:02 | Fix to the documentation on sqlite3_create_function. Ticket #899. (CVS 2128) check-in: 4ab1d012 user: drh tags: trunk | |
| 20:44 | Avoid excess heap usage when copying expressions. Ticket #979. (CVS 2127) check-in: d10560c7 user: drh tags: trunk | |
Changes
Changes to www/capi3ref.tcl.
1
2
3
4
5
6
7
8
...
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
|
set rcsid {$Id: capi3ref.tcl,v 1.15 2004/11/18 02:04:10 drh Exp $}
source common.tcl
header {C/C++ Interface For SQLite Version 3}
puts {
<h2>C/C++ Interface For SQLite Version 3</h2>
}
proc api {name prototype desc {notused x}} {
................................................................................
The first argument is the database handle that the new function or
aggregate is to be added to. If a single program uses more than one
database handle internally, then user functions or aggregates must
be added individually to each database handle with which they will be
used.
The third parameter is the number of arguments that the function or
aggregate takes. If this parameter is negative, then the function or
aggregate may take any number of arguments.
The fourth parameter, eTextRep, specifies what type of text arguments
this function prefers to receive. Any function should be able to work
work with UTF-8, UTF-16le, or UTF-16be. But some implementations may be
more efficient with one representation than another. Users are allowed
to specify separate implementations for the same function which are called
|
|
|
|
1
2
3
4
5
6
7
8
...
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
|
set rcsid {$Id: capi3ref.tcl,v 1.16 2004/11/20 21:02:14 drh Exp $}
source common.tcl
header {C/C++ Interface For SQLite Version 3}
puts {
<h2>C/C++ Interface For SQLite Version 3</h2>
}
proc api {name prototype desc {notused x}} {
................................................................................
The first argument is the database handle that the new function or
aggregate is to be added to. If a single program uses more than one
database handle internally, then user functions or aggregates must
be added individually to each database handle with which they will be
used.
The third parameter is the number of arguments that the function or
aggregate takes. If this parameter is -1 then the function or
aggregate may take any number of arguments.
The fourth parameter, eTextRep, specifies what type of text arguments
this function prefers to receive. Any function should be able to work
work with UTF-8, UTF-16le, or UTF-16be. But some implementations may be
more efficient with one representation than another. Users are allowed
to specify separate implementations for the same function which are called
|