From f5628d782590e2807f3ad8125e2936642cac7c35 Mon Sep 17 00:00:00 2001
From: danielk1977
-SQLite version 3.0 will be a new version of SQLite, derived from
+SQLite version 3.0 is a new version of SQLite, derived from
the SQLite 2.8.13 code base, but with an incompatible file format
and API.
-SQLite version 3.0 is intended to answer the increasing demand
-for the following features:
+SQLite version 3.0 was created to answer demand for the following features:
-It became necessary to move to version 3.0
-to implement these features because each
-requires incompatible changes to the database file format. Other
-incompatible changes, such as a cleanup of the API, were introduced
-at the same time under the theory that it is best to get your
-incompatible changes out of the way all at once.
+It was necessary to move to version 3.0 to implement these features because
+each requires incompatible changes to the database file format. Other
+incompatible changes, such as a cleanup of the API, were introduced at the
+same time under the theory that it is best to get your incompatible changes
+out of the way all at once.
The API for version 3.0 is similar to the version 2.X API,
but with some important changes. Most noticeably, the "sqlite_"
prefix that occurs on the beginning of all API functions and data
-structures will be changed to "sqlite3_".
-This will avoid confusion between the two APIs and allow
-linking against both SQLite 2.X and SQLite 3.0 at the same time,
-if desired.
+structures are changed to "sqlite3_".
+This avoids confusion between the two APIs and allows linking against both
+SQLite 2.X and SQLite 3.0 at the same time.
There is no agreement on what the C datatype for a UTF-16
string should be. Therefore, SQLite uses a generic type of void*
-to refer to UTF-16 strings.
-Client software can cast the void*
+to refer to UTF-16 strings. Client software can cast the void*
to whatever datatype is appropriate for their system.
1.0 Overview
@@ -21,29 +20,26 @@ for the following features:
-The sqlite3_errcode() routine will return the result code for the most -recent major API call. sqlite3_errmsg() will return an English-language -text error message for the most recent error. The error message will -be represented in UTF-8 and will be ephemeral - it could disappear on +The sqlite3_errcode() routine returns a result code for the most +recent major API call. sqlite3_errmsg() returns an English-language +text error message for the most recent error. The error message is +represented in UTF-8 and will be ephemeral - it could disappear on the next call to any SQLite API function. sqlite3_errmsg16() works like sqlite3_errmsg() except that it returns the error message represented as UTF-16 in host native byte order. @@ -178,8 +174,8 @@ calls to the prepared statement interface.
The sqlite3_prepare interface compiles a single SQL statement into byte code -for later execution. -This interface is now the preferred way of accessing the database. +for later execution. This interface is now the preferred way of accessing +the database.