CopyHandler

Clone
ixen <ixen@copyhandler.com>
committed
3526dc6
on 19 Sep 16
Added and fixed unit tests related to copy-of naming functionality (CH-264).
LoggerImprovements + 5 more
ext/sqlite3/sqlite3.h (+9 -5)
104 104 ** with the value (X*1000000 + Y*1000 + Z) where X, Y, and Z are the same
105 105 ** numbers used in [SQLITE_VERSION].)^
106 106 ** The SQLITE_VERSION_NUMBER for any given release of SQLite will also
107 107 ** be larger than the release from which it is derived.  Either Y will
108 108 ** be held constant and Z will be incremented or else Y will be incremented
109 109 ** and Z will be reset to zero.
110 110 **
111 111 ** Since [version 3.6.18] ([dateof:3.6.18]),
112 112 ** SQLite source code has been stored in the
113 113 ** <a href="http://www.fossil-scm.org/">Fossil configuration management
114 114 ** system</a>.  ^The SQLITE_SOURCE_ID macro evaluates to
115 115 ** a string which identifies a particular check-in of SQLite
116 116 ** within its configuration management system.  ^The SQLITE_SOURCE_ID
117 117 ** string contains the date and time of the check-in (UTC) and an SHA1
118 118 ** hash of the entire source tree.
119 119 **
120 120 ** See also: [sqlite3_libversion()],
121 121 ** [sqlite3_libversion_number()], [sqlite3_sourceid()],
122 122 ** [sqlite_version()] and [sqlite_source_id()].
123 123 */
124   #define SQLITE_VERSION        "3.16.0"
125   #define SQLITE_VERSION_NUMBER 3016000
126   #define SQLITE_SOURCE_ID      "2017-01-02 11:57:58 04ac0b75b1716541b2b97704f4809cb7ef19cccf"
  124 #define SQLITE_VERSION        "3.16.2"
  125 #define SQLITE_VERSION_NUMBER 3016002
  126 #define SQLITE_SOURCE_ID      "2017-01-06 16:32:41 a65a62893ca8319e89e48b8a38cf8a59c69a8209"
127 127
128 128 /*
129 129 ** CAPI3REF: Run-Time Library Version Numbers
130 130 ** KEYWORDS: sqlite3_version sqlite3_sourceid
131 131 **
132 132 ** These interfaces provide the same information as the [SQLITE_VERSION],
133 133 ** [SQLITE_VERSION_NUMBER], and [SQLITE_SOURCE_ID] C preprocessor macros
134 134 ** but are associated with the library instead of the header file.  ^(Cautious
135 135 ** programmers might include assert() statements in their application to
136 136 ** verify that values returned by these interfaces match the macros in
137 137 ** the header, and thus ensure that the application is
138 138 ** compiled with matching library and header files.
139 139 **
140 140 ** <blockquote><pre>
141 141 ** assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER );
142 142 ** assert( strcmp(sqlite3_sourceid(),SQLITE_SOURCE_ID)==0 );
143 143 ** assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 );
144 144 ** </pre></blockquote>)^
145 145 **
146 146 ** ^The sqlite3_version[] string constant contains the text of [SQLITE_VERSION]
 
3879 3879 ** [sqlite3_bind_parameter_count()], and
3880 3880 ** [sqlite3_bind_parameter_name()].
3881 3881 */
3882 3882 SQLITE_API int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
3883 3883
3884 3884 /*
3885 3885 ** CAPI3REF: Reset All Bindings On A Prepared Statement
3886 3886 ** METHOD: sqlite3_stmt
3887 3887 **
3888 3888 ** ^Contrary to the intuition of many, [sqlite3_reset()] does not reset
3889 3889 ** the [sqlite3_bind_blob | bindings] on a [prepared statement].
3890 3890 ** ^Use this routine to reset all host parameters to NULL.
3891 3891 */
3892 3892 SQLITE_API int sqlite3_clear_bindings(sqlite3_stmt*);
3893 3893
3894 3894 /*
3895 3895 ** CAPI3REF: Number Of Columns In A Result Set
3896 3896 ** METHOD: sqlite3_stmt
3897 3897 **
3898 3898 ** ^Return the number of columns in the result set returned by the
3899   ** [prepared statement]. ^This routine returns 0 if pStmt is an SQL
3900   ** statement that does not return data (for example an [UPDATE]).
  3899 ** [prepared statement]. ^If this routine returns 0, that means the
  3900 ** [prepared statement] returns no data (for example an [UPDATE]).
  3901 ** ^However, just because this routine returns a positive number does not
  3902 ** mean that one or more rows of data will be returned.  ^A SELECT statement
  3903 ** will always have a positive sqlite3_column_count() but depending on the
  3904 ** WHERE clause constraints and the table content, it might return no rows.
3901 3905 **
3902 3906 ** See also: [sqlite3_data_count()]
3903 3907 */
3904 3908 SQLITE_API int sqlite3_column_count(sqlite3_stmt *pStmt);
3905 3909
3906 3910 /*
3907 3911 ** CAPI3REF: Column Names In A Result Set
3908 3912 ** METHOD: sqlite3_stmt
3909 3913 **
3910 3914 ** ^These routines return the name assigned to a particular column
3911 3915 ** in the result set of a [SELECT] statement.  ^The sqlite3_column_name()
3912 3916 ** interface returns a pointer to a zero-terminated UTF-8 string
3913 3917 ** and sqlite3_column_name16() returns a pointer to a zero-terminated
3914 3918 ** UTF-16 string.  ^The first parameter is the [prepared statement]
3915 3919 ** that implements the [SELECT] statement. ^The second parameter is the
3916 3920 ** column number.  ^The leftmost column is number 0.
3917 3921 **
3918 3922 ** ^The returned string pointer is valid until either the [prepared statement]
3919 3923 ** is destroyed by [sqlite3_finalize()] or until the statement is automatically
3920 3924 ** reprepared by the first call to [sqlite3_step()] for a particular run