Welcome to the SQLitening support forums!
Started by Paul Squires, April 16, 2008, 11:28:40 am
'** The sqlite3_prepare_v2() and sqlite3_prepare16_v2() interfaces are'** recommended for all new programs. The two older interfaces are retained'** for backwards compatibility, but their use is discouraged.'** In the "v2" interfaces, the prepared statement'** that is returned (the [sqlite3_stmt] object) contains a copy of the'** original SQL text. This causes the [sqlite3_step()] interface to'** behave a differently in two ways:'**'** <ol>'** <li>'** If the database schema changes, instead of returning [SQLITE_SCHEMA] as it'** always used to do, [sqlite3_step()] will automatically recompile the SQL'** statement and try to run it again. If the schema has changed in a way'** that makes the statement no longer valid, [sqlite3_step()] will still'** return [SQLITE_SCHEMA]. But unlike the legacy behavior, [SQLITE_SCHEMA] is'** now a fatal error. Calling [sqlite3_prepare_v2()] again will not make the'** error go away. Note: use [sqlite3_errmsg()] to find the text of the parsing'** error that results in an [SQLITE_SCHEMA] return.'** </li>'**'** <li>'** When an error occurs,'** [sqlite3_step()] will return one of the detailed'** [SQLITE_ERROR | result codes] or'** [SQLITE_IOERR_READ | extended result codes] such as directly.'** The legacy behavior was that [sqlite3_step()] would only return a generic'** [SQLITE_ERROR] result code and you would have to make a second call to'** [sqlite3_reset()] in order to find the underlying cause of the problem.'** With the "v2" prepare interfaces, the underlying reason for the error is'** returned immediately.'** </li>'** </ol>
Quote from: David on May 09, 2008, 04:55:32 pmAre there any function in order to go to a specific row on the recordset? something like sql3_rsMoveTo ?
QuoteI know all recordset is treated as string. Are there any function in order to know what kind of field is a column?