/ Check-in [7ded90ba]
Login

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

Overview
Comment:Fix some off-by-one errors in the comments for API functions create_function() and value_blob(). No changes to code or tests.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 7ded90baeb75db5af83345cd2c31211cbee1e91b
User & Date: dan 2010-12-29 10:49:47
Context
2010-12-29
18:24
Have testfixture invoke C routine Zipvfs_Init() when creating a new interpreter if SQLITE_ENABLE_ZIPVFS is defined. check-in: 430635da user: dan tags: trunk
10:49
Fix some off-by-one errors in the comments for API functions create_function() and value_blob(). No changes to code or tests. check-in: 7ded90ba user: dan tags: trunk
2010-12-24
15:49
Reduce the number of calls to sqlite3_realloc() made by fts3 when querying for position information of a term prefix. check-in: 7088d945 user: dan tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to src/sqlite.h.in.

  3407   3407   ** will pick the one that involves the least amount of data conversion.
  3408   3408   ** If there is only a single implementation which does not care what text
  3409   3409   ** encoding is used, then the fourth argument should be [SQLITE_ANY].
  3410   3410   **
  3411   3411   ** ^(The fifth parameter is an arbitrary pointer.  The implementation of the
  3412   3412   ** function can gain access to this pointer using [sqlite3_user_data()].)^
  3413   3413   **
  3414         -** ^The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
         3414  +** ^The sixth, seventh and eighth parameters, xFunc, xStep and xFinal, are
  3415   3415   ** pointers to C-language functions that implement the SQL function or
  3416   3416   ** aggregate. ^A scalar SQL function requires an implementation of the xFunc
  3417   3417   ** callback only; NULL pointers must be passed as the xStep and xFinal
  3418   3418   ** parameters. ^An aggregate SQL function requires an implementation of xStep
  3419   3419   ** and xFinal and NULL pointer must be passed for xFunc. ^To delete an existing
  3420   3420   ** SQL function or aggregate, pass NULL poiners for all three function
  3421   3421   ** callbacks.
  3422   3422   **
  3423         -** ^(If the tenth parameter to sqlite3_create_function_v2() is not NULL,
         3423  +** ^(If the ninth parameter to sqlite3_create_function_v2() is not NULL,
  3424   3424   ** then it is destructor for the application data pointer. 
  3425   3425   ** The destructor is invoked when the function is deleted, either by being
  3426   3426   ** overloaded or when the database connection closes.)^
  3427   3427   ** ^The destructor is also invoked if the call to
  3428   3428   ** sqlite3_create_function_v2() fails.
  3429   3429   ** ^When the destructor callback of the tenth parameter is invoked, it
  3430   3430   ** is passed a single argument which is a copy of the application data 
................................................................................
  3520   3520   ** The C-language implementation of SQL functions and aggregates uses
  3521   3521   ** this set of interface routines to access the parameter values on
  3522   3522   ** the function or aggregate.
  3523   3523   **
  3524   3524   ** The xFunc (for scalar functions) or xStep (for aggregates) parameters
  3525   3525   ** to [sqlite3_create_function()] and [sqlite3_create_function16()]
  3526   3526   ** define callbacks that implement the SQL functions and aggregates.
  3527         -** The 4th parameter to these callbacks is an array of pointers to
         3527  +** The 3rd parameter to these callbacks is an array of pointers to
  3528   3528   ** [protected sqlite3_value] objects.  There is one [sqlite3_value] object for
  3529   3529   ** each parameter to the SQL function.  These routines are used to
  3530   3530   ** extract values from the [sqlite3_value] objects.
  3531   3531   **
  3532   3532   ** These routines work only with [protected sqlite3_value] objects.
  3533   3533   ** Any attempt to use these routines on an [unprotected sqlite3_value]
  3534   3534   ** object results in undefined behavior.