mirror of
https://github.com/sqlite/sqlite.git
synced 2025-11-18 10:21:03 +03:00
Enhance user function API to support association of meta-data with constant
arguments and the specification of text encoding preference. The LIKE operator takes advantage of both. (CVS 1534) FossilOrigin-Name: 92337d8f79b9754cd61c73e7db2e792a1f482f50
This commit is contained in:
@@ -12,7 +12,7 @@
|
||||
** This header file defines the interface that the SQLite library
|
||||
** presents to client programs.
|
||||
**
|
||||
** @(#) $Id: sqlite.h.in,v 1.92 2004/06/05 10:22:18 danielk1977 Exp $
|
||||
** @(#) $Id: sqlite.h.in,v 1.93 2004/06/06 09:44:04 danielk1977 Exp $
|
||||
*/
|
||||
#ifndef _SQLITE_H_
|
||||
#define _SQLITE_H_
|
||||
@@ -835,6 +835,13 @@ int sqlite3_reset(sqlite3_stmt *pStmt);
|
||||
** aggregate takes. If this parameter is negative, then the function or
|
||||
** aggregate may take any number of arguments.
|
||||
**
|
||||
** If the fourth parameter is non-zero, this indicates that the function is
|
||||
** more likely to handle text in UTF-16 encoding than UTF-8. This does not
|
||||
** change the behaviour of the programming interface. However, if two
|
||||
** versions of the same function are registered, one with eTextRep non-zero
|
||||
** and the other zero, SQLite invokes the version likely to minimize
|
||||
** conversions between unicode encodings.
|
||||
**
|
||||
** The seventh, eighth and ninth parameters, xFunc, xStep and xFinal, are
|
||||
** pointers to user implemented C functions that implement the user
|
||||
** function or aggregate. A scalar function requires an implementation of
|
||||
|
||||
Reference in New Issue
Block a user