DbProviderFactory Support @@ -95,11 +83,11 @@ <DbProviderFactories> <remove invariant="System.Data.SQLite"/> <add name="SQLite Data Provider" invariant="System.Data.SQLite" description=".Net Framework Data Provider for SQLite" type="System.Data.SQLite.SQLiteFactory, System.Data.SQLite, - Version=1.0.67.0, Culture=neutral, + Version=1.0.74.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139"/> </DbProviderFactories> </system.data> </configuration> @@ -115,15 +103,15 @@ }

Index: Doc/Extra/designer.html ================================================================== --- Doc/Extra/designer.html +++ Doc/Extra/designer.html @@ -1,24 +1,12 @@ Design-Time Support - - - + - - - - - - - - - - - +

Design-Time Support @@ -75,15 +63,15 @@ You can revert back to the Access designer simply by re-running the install.exe program and un-checking the boxes.

Index: Doc/Extra/lang_altertable.html ================================================================== --- Doc/Extra/lang_altertable.html +++ Doc/Extra/lang_altertable.html @@ -1,24 +1,12 @@ ALTER TABLE - - - + - - - - - - - - - - - +

Index: Doc/Extra/lang_analyze.html ================================================================== --- Doc/Extra/lang_analyze.html +++ Doc/Extra/lang_analyze.html @@ -1,24 +1,12 @@ ANALYZE - - - + - - - - - - - - - - - +

ALTER TABLE

Index: Doc/Extra/lang_attach.html ================================================================== --- Doc/Extra/lang_attach.html +++ Doc/Extra/lang_attach.html @@ -1,24 +1,12 @@ ATTACH DATABASE - - - + - - - - - - - - - - - +

ANALYZE

Index: Doc/Extra/lang_comment.html ================================================================== --- Doc/Extra/lang_comment.html +++ Doc/Extra/lang_comment.html @@ -1,24 +1,12 @@ comment - - - + - - - - - - - - - - - +

ATTACH DATABASE

Index: Doc/Extra/lang_conflict.html ================================================================== --- Doc/Extra/lang_conflict.html +++ Doc/Extra/lang_conflict.html @@ -1,24 +1,12 @@ ON CONFLICT - - - + - - - - - - - - - - - +

comment

Index: Doc/Extra/lang_createindex.html ================================================================== --- Doc/Extra/lang_createindex.html +++ Doc/Extra/lang_createindex.html @@ -1,24 +1,12 @@ CREATE INDEX - - - + - - - - - - - - - - - +

ON CONFLICT clause

Index: Doc/Extra/lang_createtable.html ================================================================== --- Doc/Extra/lang_createtable.html +++ Doc/Extra/lang_createtable.html @@ -1,24 +1,12 @@ CREATE TABLE - - - + - - - - - - - - - - - +

CREATE INDEX

Index: Doc/Extra/lang_createtrigger.html ================================================================== --- Doc/Extra/lang_createtrigger.html +++ Doc/Extra/lang_createtrigger.html @@ -1,24 +1,12 @@ CREATE TABLE - - - + - - - - - - - - - - - +

CREATE TABLE

Index: Doc/Extra/lang_createview.html ================================================================== --- Doc/Extra/lang_createview.html +++ Doc/Extra/lang_createview.html @@ -1,24 +1,12 @@ CREATE VIEW - - - + - - - - - - - - - - - +

CREATE TRIGGER

Index: Doc/Extra/lang_createvtab.html ================================================================== --- Doc/Extra/lang_createvtab.html +++ Doc/Extra/lang_createvtab.html @@ -1,24 +1,12 @@ CREATE VIRTUAL TABLE - - - + - - - - - - - - - - - +

CREATE VIEW

Index: Doc/Extra/lang_datetime.html ================================================================== --- Doc/Extra/lang_datetime.html +++ Doc/Extra/lang_datetime.html @@ -1,24 +1,12 @@ DateTime Functions - - - + - - - - - - - - - - - +

CREATE VIRTUAL TABLE

Index: Doc/Extra/lang_delete.html ================================================================== --- Doc/Extra/lang_delete.html +++ Doc/Extra/lang_delete.html @@ -1,24 +1,12 @@ DELETE - - - + - - - - - - - - - - - +

Date and Time Functions

Index: Doc/Extra/lang_detach.html ================================================================== --- Doc/Extra/lang_detach.html +++ Doc/Extra/lang_detach.html @@ -1,24 +1,12 @@ DETACH - - - + - - - - - - - - - - - +

DELETE

Index: Doc/Extra/lang_dropindex.html ================================================================== --- Doc/Extra/lang_dropindex.html +++ Doc/Extra/lang_dropindex.html @@ -1,24 +1,12 @@ DROP INDEX - - - + - - - - - - - - - - - +

DETACH

Index: Doc/Extra/lang_droptable.html ================================================================== --- Doc/Extra/lang_droptable.html +++ Doc/Extra/lang_droptable.html @@ -1,24 +1,12 @@ DROP TABLE - - - + - - - - - - - - - - - +

DROP INDEX

Index: Doc/Extra/lang_droptrigger.html ================================================================== --- Doc/Extra/lang_droptrigger.html +++ Doc/Extra/lang_droptrigger.html @@ -1,24 +1,12 @@ DROP TRIGGER - - - + - - - - - - - - - - - +

DROP TABLE

Index: Doc/Extra/lang_dropview.html ================================================================== --- Doc/Extra/lang_dropview.html +++ Doc/Extra/lang_dropview.html @@ -1,24 +1,12 @@ DROP VIEW - - - + - - - - - - - - - - - +

DROP TRIGGER

Index: Doc/Extra/lang_explain.html ================================================================== --- Doc/Extra/lang_explain.html +++ Doc/Extra/lang_explain.html @@ -1,24 +1,12 @@ EXPLAIN - - - + - - - - - - - - - - - +

DROP VIEW

Index: Doc/Extra/lang_expr.html ================================================================== --- Doc/Extra/lang_expr.html +++ Doc/Extra/lang_expr.html @@ -1,30 +1,18 @@ expression - - - + - - - - - - - - - - - +

EXPLAIN

Index: Doc/Extra/lang_insert.html ================================================================== --- Doc/Extra/lang_insert.html +++ Doc/Extra/lang_insert.html @@ -1,24 +1,12 @@ INSERT - - - + - - - - - - - - - - - +

expression

Index: Doc/Extra/lang_reindex.html ================================================================== --- Doc/Extra/lang_reindex.html +++ Doc/Extra/lang_reindex.html @@ -1,24 +1,12 @@ REINDEX - - - + - - - - - - - - - - - +

INSERT

Index: Doc/Extra/lang_replace.html ================================================================== --- Doc/Extra/lang_replace.html +++ Doc/Extra/lang_replace.html @@ -1,24 +1,12 @@ REPLACE - - - + - - - - - - - - - - - +

REINDEX

Index: Doc/Extra/lang_select.html ================================================================== --- Doc/Extra/lang_select.html +++ Doc/Extra/lang_select.html @@ -1,24 +1,12 @@ SELECT - - - + - - - - - - - - - - - +

REPLACE

Index: Doc/Extra/lang_transaction.html ================================================================== --- Doc/Extra/lang_transaction.html +++ Doc/Extra/lang_transaction.html @@ -1,24 +1,12 @@ TRANSACTIONS - - - + - - - - - - - - - - - +

SELECT

Index: Doc/Extra/lang_types.html ================================================================== --- Doc/Extra/lang_types.html +++ Doc/Extra/lang_types.html @@ -1,24 +1,12 @@ TYPES - - - + - - - - - - - - - - - +

BEGIN TRANSACTION

Index: Doc/Extra/lang_update.html ================================================================== --- Doc/Extra/lang_update.html +++ Doc/Extra/lang_update.html @@ -1,24 +1,12 @@ UPDATE - - - + - - - - - - - - - - - +

TYPES

Index: Doc/Extra/lang_vacuum.html ================================================================== --- Doc/Extra/lang_vacuum.html +++ Doc/Extra/lang_vacuum.html @@ -1,24 +1,12 @@ TYPES - - - + - - - - - - - - - - - +

UPDATE

Index: Doc/Extra/limitations.html ================================================================== --- Doc/Extra/limitations.html +++ Doc/Extra/limitations.html @@ -1,24 +1,12 @@ Provider Limitations - - - + - - - - - - - - - - - +

VACUUM

Provider Limitations @@ -108,15 +96,15 @@ other thread will block until the CommandTimeout value elapses or the other thread finishes.

ADDED Doc/Extra/ndoc.css Index: Doc/Extra/ndoc.css ================================================================== --- /dev/null +++ Doc/Extra/ndoc.css @@ -0,0 +1,572 @@ +.userDataStyle +{ + behavior: url(#default#userData); +} + +@media all +{ + tool\:tip{behavior: url(tooltip.htc)} +} + +body +{ + background: #FFFFFF; + color: #000000; + font-family: Verdana; + font-size: medium; + font-style: normal; + font-weight: normal; + margin: 0px; + width: 100%; +} + +a +{ + color: #0000FF; +} + +a:visited +{ + color: #0000FF; +} + +a:hover +{ + color: #3366FF; +} + +div#mainSection +{ + font-size: 70%; + width: 100%; +} + +div#mainBody +{ + font-size: 90%; + margin-left: 15px; + margin-top: 10px; + padding-bottom: 20px; +} +div#mainBody p, div#mainBody ol, div#mainBody ul, div#mainBody dl +{ + padding-right: 5; +} + +div#header +{ + background-color: #D4DFFF; + padding: 0px; + width: 100%; +} + +div#header table +{ + border-bottom: solid 1px #C8CDDE; + width: 100%; +} + +span#runningHeaderText +{ + color: #003399; + font-size: 90%; + padding-left: 13px; +} + + +span#nsrTitle +{ + color: #003399; + font-size: 120%; + font-weight: bold; + padding-left: 13px; +} + +div#header table td +{ + color: #0000FF; + font-size: 70%; + margin-top: 0px; + margin-bottom: 0px; + padding-right: 20px; +} + +div#header table tr#headerTableRow3 td +{ + padding-bottom: 2px; + padding-top: 5px; + padding-left: 15px; +} + +div#header table#bottomTable +{ + border-top: solid 1px #FFFFFF; + text-align: left; + padding-left: 15px; +} + +div#footer +{ + font-size: 90%; + margin: 0px; + padding: 2px; + width: 100%; +} + +hr#footerHR +{ + border-bottom: solid 1px #EEEEFF; + border-top: solid 1px #C8CDDE; + height: 3px; + color: #D4DFFF; +} +/* +div.saveHistory +{ + behavior:url(#default#saveHistory); +} +*/ +div.section +{ + padding-top: 2px; + padding-bottom: 2px; + padding-left: 16px; + padding-right: 15px; + width: 100%; +} + +.heading +{ + font-weight: bold; + margin-top: 18px; + margin-bottom: 8px; +} + +h1.heading +{ + color: #003399; + font-size: 130%; +} + +.subHeading +{ + font-weight: bold; + margin-bottom: 4px; +} + +h3.subHeading +{ + color: #000000; + font-size: 120%; + font-weight: normal; +} + +h4.subHeading +{ + color: #000000; + font-size: 100%; +} + +img.toggle +{ + border: none; + margin-right: 5px; +} + +img.copyCodeImage +{ + border: none; + margin: 1px; + margin-right: 3px; +} + +img.downloadCodeImage +{ + border: none; + margin-right: 3px; +} + +img.viewCodeImage +{ + border: none; + margin-right: 3px; +} + +img.note +{ + border: none; + margin-right: 3px; +} + +img#languageFilterImage +{ + border: none; + margin-left: 10px; + vertical-align: middle; +} + +img#membersOptionsFilterImage +{ + border: none; + margin-left: 10px; + vertical-align: middle; +} + +img#toggleAllImage +{ + margin-left: 4px; + vertical-align: middle; +} + +div#mainSection table +{ + border: none; + font-size: 100%; + width: 100%; + margin-top: 5px; + margin-bottom: 5px; +} + +div#mainSection table tr +{ + vertical-align: top; +} + +div#mainSection table th +{ + background-color: #EFEFF7; + border-bottom: solid 1px #C8CDDE; + color: #000066; + padding-left: 5px; + padding-right: 5px; + text-align: left; +} + +div#mainSection table td +{ + background-color: #F7F7FF; + border-bottom: solid 1px #D5D5D3; + /*border-left: solid 1px #D5D5D3;*/ + padding-left: 5px; + padding-right: 5px; + margin: 1px; +} + +div#mainSection table td.imageCell +{ + white-space: nowrap; + /*width: 1%;*/ +} + +div#mainSection table td.nameCell +{ + white-space: nowrap; +} + +div.code table +{ + border: none; + font-size: 95%; + margin-bottom: 5px; + margin-top:-.4em; + width: 100%; +} + +div.code table th +{ + background: #EFEFF7; + border-bottom: solid 1px #C8CDDE; + color: #000066; + font-weight: bold; + padding-left: 5px; + padding-right: 5px; +} + +div.code table td +{ + background: #F7F7FF; + border-top: solid 1px #FFFFFF; + padding-left: 5px; + padding-right: 5px; + padding-top: 5px; + padding-bottom: 15px; +} + +div.code table td.syntax +{ + font-family: Monospace, Courier New, Courier; + font-size: 105%; + color: #000066; + white-space: nowrap; +} + +div.code table td.message +{ +} + +div.alert table +{ + border: none; + font-size: 100%; + width: 100%; +} + +div.alert table th +{ + background: #EFEFF7; + border-bottom-width: 0px; + color: #000066; + padding-left: 5px; + padding-right: 5px; +} + +div.alert table td +{ + background: #F7F7FF; + border-top: solid 1px #FFFFFF; + padding-left: 5px; + padding-right: 5px; +} + +span.copyCode +{ + color: #0000ff; + font-size: 90%; + font-weight: normal; + cursor: hand; + float: right; + display: inline; + text-align: right; +} + +.downloadCode +{ + color: #0000ff; + font-size: 90%; + font-weight: normal; + cursor: hand; +} + +.viewCode +{ + color: #0000ff; + font-size: 90%; + font-weight: normal; + cursor: hand; +} + +code +{ + font-family: Monospace, Courier New, Courier; + font-size: 105%; + color: #000066; +} + +dl +{ + margin-top: 0px; + padding-left: 1px; +} + +dt +{ + font-style: italic; +} + +dd +{ + margin-bottom: 0px; + margin-left: 0px; +} + +ul +{ + margin-top:0px; + margin-bottom:0px; + margin-left: 17px; + list-style-type: disc; +} + +ul ul +{ + margin-bottom: 4px; + margin-left: 17px; + margin-top: 3px; + list-style-type: disc; +} + +ol +{ + margin-top:0px; + margin-bottom:0px; + margin-left: 28px; + list-style-type: decimal; +} + +ol ol +{ + margin-bottom: 4px; + margin-left: 24px; + margin-top: 3px; + list-style-type: lower-alpha; +} + +li +{ + margin-top:-2px; + margin-bottom: 3px; +} + +p +{ + margin-top: 10px; + margin-bottom: 5px; +} + +.tip +{ + color: #0000FF; + font-style: italic; + cursor: hand; + text-decoration: underline; +} + +.languageFilter +{ + color: #0000FF; + cursor: hand; + text-decoration: underline; + padding-bottom: 4px; +} + +.math +{ + font-family: Times New Roman; + font-size: 125%; +} + +.sourceCodeList +{ + font-family: Verdana; + font-size: 90%; +} + +pre.viewCode +{ + width: 100%; + overflow: auto; +} + +MSHelp\:link +{ + text-decoration: underline; + color: #0000ff; + hoverColor: #3366ff; + filterString: ; +} + + +/*----------------------------------------------*/ +/* +.attribute a:link +{ + color: #000088; + text-decoration: none; +} +.attribute a:visited +{ + color: #000088; + text-decoration: none; +} +.attribute a:hover +{ + color: #3366ff; +} + +.attribute MSHelp\:link + { + text-decoration: underline; + color: #0000ff; + hoverColor: #3366ff; + filterString: ; + } +*/ +.missing +{ + color: Red; + font-weight: bold; +} +div.hier +{ + margin-top: 0.5em; + margin-right: 0.0em; + margin-bottom: 0.5em; + margin-left: 1.0em; +} +div#mainSection table.hier +{ + border: none; + font-size: 100%; + padding: 0px; + margin: 0px; + border-collapse: collapse; + width: auto; +} +div#mainSection table.hier tr +{ + padding: 0px; + margin: 0px; +} +div#mainSection table.hier td +{ + border: none; + vertical-align: top; + padding: 0px; + margin: 50px; + background-color: transparent; +} + +div.code table td span.attribute +{ + padding: 0px; + margin: 0px; +} + +p.inheritDoc +{ + padding: 2px; + margin: 0px; + background-color: #FFFFE0; + border-top: solid 1px #E0E0C0; +} +p.inheritSource +{ + padding: 0px 2px; + margin: 0px; + font-size: 85%; + background-color: #F0F0D0; + color: #606050; +} +span.autoText +{ + padding: 2px; + margin: 0px; + background-color: #E0FFE0; + color: #206020; +} + +p.missing +{ + padding: 2px; + margin: 0px; + font-size: 85%; + background-color: #FFE0E0; + color: #800000; + font-weight: bold; +} + +.topicstatus /* Topic Status Boilerplate class */ + { + display: block; + color: red; + } Index: Doc/Extra/optimizing.html ================================================================== --- Doc/Extra/optimizing.html +++ Doc/Extra/optimizing.html @@ -1,24 +1,12 @@ Optimizing Your Queries - - - + - - - - - - - - - - - +

Optimizing for SQLite @@ -132,15 +120,15 @@ line.

Index: Doc/Extra/pragma.html ================================================================== --- Doc/Extra/pragma.html +++ Doc/Extra/pragma.html @@ -1,24 +1,12 @@ PRAGMA - - - + - - - - - - - - - - - +

Index: Doc/Extra/syntax.html ================================================================== --- Doc/Extra/syntax.html +++ Doc/Extra/syntax.html @@ -1,24 +1,12 @@ SQLite Query Syntax - - - + - - - - - - - - - - - +

PRAGMA

Index: Doc/Extra/version.html ================================================================== --- Doc/Extra/version.html +++ Doc/Extra/version.html @@ -1,24 +1,12 @@ Version History - - - + - - - - - - - - - - - +

SQLite Query Syntax

Version History @@ -53,23 +41,71 @@

Version History

1.0.74.0 - July 4, 2011

Updated to SQLite 3.7.7.1 [af0d91adf4].
Fix incorrect hard-coded .NET Framework version information SQLiteFactory_Linq.cs that was causing IServiceProvider.GetService to fail when running against the .NET Framework 3.5.
Fix all XML documentation warnings.
Restore support for the mixed-mode assembly (i.e. the one that can be registered in the Global Assembly Cache).
Restore support for the Compact Framework.
Remove unused "using" statements from the System.Data.SQLite and System.Data.SQLite.Linq projects.
Remove hard-coded System.Data.SQLite.Linq version from SQLiteFactory_Linq.cs
Modify the setup to support bundled packages (i.e. with the mixed-mode assembly) and standard packages (i.e. with the managed assembly separate from the native interop library).
Disable the ability to register with the Global Assembly Cache in the standard setup package (i.e. it is available in the bundled setup only).
Remove PATH modification from the setup.
Modify the naming scheme for the source, setup, and binary packages to allow for the necessary variants.
In the build automation, attempt to automatically detect if Visual Studio 2008 and/or 2010 are installed and support building binaries for both at once, when available.
Add release automation to build the source, setup, and binary packages in all supported build variants.
Add the testlinq project to the new build system and make it work properly with Visual Studio 2008 and 2010.

1.0.73.0 - June 2, 2011

Updated to SQLite 3.7.6.3 [ed1da510a2].
Minor optimization to GetBytes(). Fix for [8c1650482e].
Update various assembly information settings.
Correct System.Data.SQLite.Linq version and resource information. Fix for [6489c5a396] and [133daf50d6].
Moved log handler from SQLiteConnection object to SQLiteFactory object to prevent if from being prematurely GCed.
We should block x64 installs on x86 and we should install native only if the setup package itself is native. Fix for [e058ce156e].

1.0.72.0 - May 1, 2011

Add the correct directory to the path. Fix for [50515a0c8e].

1.0.71.0 - April 27, 2011

Updated to SQLite 3.7.6+ [1bd1484cd7] to get additional Windows error logging.
Updated setup to optionally add install directory to PATH if GAC option selected.

1.0.69.0 - April 12, 2011

Code merge with SQLite 3.7.6
New VS2008 and VS2010 solution files
Build and packaging automation
New Inno Setup files
Designer support currently not ready for release

1.0.68.0 - February 2011

Code merge with SQLite 3.7.5
Continuing work on supporting Visual Studio 2010

1.0.67.0 - January 3, 2011

Code merge with SQLite 3.7.4
Continuing work on supporting Visual Studio 2010

1.0.66.1 - August 1, 2010

Code merge with SQLite 3.7.0.1
Re-enabled VS2005 designer support, broken in previous versions during the 2008 transition
Implemented new forms of Take/Skip in the EF framework courtesy jlsantiago
Added "Foreign Keys" to the connection string parameters
Added the Truncate option to the Journal Modes enumeration

1.0.66.1 - August 1, 2010

Code merge with SQLite 3.7.0.1
Re-enabled VS2005 designer support, broken in previous versions during the 2008 transition
Implemented new forms of Take/Skip in the EF framework courtesy jlsantiago
Added "Foreign Keys" to the connection string parameters
Added the Truncate option to the Journal Modes enumeration

1.0.66.0 - April 18, 2010

Code merge with SQLite 3.6.23.1
Fixed a bug in the installer that accidentally modified the machine.config on .NET versions prior to 2.0, invaliding the config file.
Fixed INTERSECT and EXCEPT union query generation in EF

Index: Doc/Extra/welcome.html ================================================================== --- Doc/Extra/welcome.html +++ Doc/Extra/welcome.html @@ -1,29 +1,17 @@ Introduction - - - + - - - - - - - - - - - +

About SQLite.NET

This class library is an ADO.NET 2.0 wrapper around the popular (and free!) +

This class library is an ADO.NET wrapper around the popular (and free!) SQLite database engine. For information on SQL syntax, features of SQLite and a good understanding of how it works and what it does, I highly recommend heading over to sqlite.org and reading the documentation there.

The C# provider, the very minor C code modifications to SQLite, documentation and @@ -87,11 +75,11 @@

SQLite.NET Provider Features

This SQLite provider implements every feature of the underlying SQLite database engine without omission. Here's a brief summary:

- Written from scratch on VS2005/2008 specifically for ADO.NET 2.0, implenting all the + Written from scratch on VS2005/2008 specifically for ADO.NET, implenting all the base classes and features recently introduced in the framework, including automatic transaction enlistment.
Supports the Full and Compact .NET Framework, as well as native C/C++ development. 100% binary compatible with the original sqlite3.dll.
Full support for Mono via a "managed only" provider that runs against the official SQLite 3.6.1 or higher library.

Distributing the Binaries (Compact Framework)

System.Data.SQLite.DLL and SQLite.Interop.XXX.DLL must be deployed on the Compact Framework. The XXX is the build number of the - System.Data.SQLite library (e.g. "059"). SQLite.Interop.XXX is a fully + System.Data.SQLite library (e.g. "074"). SQLite.Interop.XXX is a fully native assembly compiled for the ARM processor, and System.Data.SQLite is the fully-managed Compact Framework assembly.

Index: Doc/SQLite.NET.chm ================================================================== --- Doc/SQLite.NET.chm +++ Doc/SQLite.NET.chm cannot compute difference between binary files ADDED Doc/SQLite.NET.hhc Index: Doc/SQLite.NET.hhc ================================================================== --- /dev/null +++ Doc/SQLite.NET.hhc @@ -0,0 +1,155 @@ + + + + + + +

SQLITE_CONFIG_SINGLETHREAD

There are no arguments to this option. ^This option sets the ** [threading mode] to Single-thread. In other words, it disables ** all mutexing and puts SQLite into a mode where it can only be used ** by a single thread. ^If SQLite is compiled with ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then @@ -1790,11 +1801,11 @@ ** it is not possible to change the [threading mode] from its default ** value of Single-thread and so [sqlite3_config()] will return ** [SQLITE_ERROR] if called with the SQLITE_CONFIG_SINGLETHREAD ** configuration option.

SQLITE_CONFIG_MULTITHREAD

There are no arguments to this option. ^This option sets the ** [threading mode] to Multi-thread. In other words, it disables ** mutexing on [database connection] and [prepared statement] objects. ** The application is responsible for serializing access to ** [database connections] and [prepared statements]. But other mutexes @@ -1804,11 +1815,11 @@ ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then ** it is not possible to set the Multi-thread [threading mode] and ** [sqlite3_config()] will return [SQLITE_ERROR] if called with the ** SQLITE_CONFIG_MULTITHREAD configuration option.

SQLITE_CONFIG_SERIALIZED

There are no arguments to this option. ^This option sets the ** [threading mode] to Serialized. In other words, this option enables ** all mutexes including the recursive ** mutexes on [database connection] and [prepared statement] objects. ** In this mode (which is the default when SQLite is compiled with @@ -1820,27 +1831,27 @@ ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then ** it is not possible to set the Serialized [threading mode] and ** [sqlite3_config()] will return [SQLITE_ERROR] if called with the ** SQLITE_CONFIG_SERIALIZED configuration option.

SQLITE_CONFIG_MALLOC

^(This option takes a single argument which is a pointer to an ** instance of the [sqlite3_mem_methods] structure. The argument specifies ** alternative low-level memory allocation routines to be used in place of ** the memory allocation routines built into SQLite.)^ ^SQLite makes ** its own private copy of the content of the [sqlite3_mem_methods] structure ** before the [sqlite3_config()] call returns.

SQLITE_CONFIG_GETMALLOC

^(This option takes a single argument which is a pointer to an ** instance of the [sqlite3_mem_methods] structure. The [sqlite3_mem_methods] ** structure is filled with the currently defined memory allocation routines.)^ ** This option can be used to overload the default memory allocation ** routines with a wrapper that simulations memory allocation failure or ** tracks memory usage, for example.

SQLITE_CONFIG_MEMSTATUS

^This option takes single argument of type int, interpreted as a ** boolean, which enables or disables the collection of memory allocation ** statistics. ^(When memory allocation statistics are disabled, the ** following SQLite interfaces become non-operational: **

@@ -1852,11 +1863,11 @@ ** ^Memory allocation statistics are enabled by default unless SQLite is ** compiled with [SQLITE_DEFAULT_MEMSTATUS]=0 in which case memory ** allocation statistics are disabled by default. **

SQLITE_CONFIG_SCRATCH

^This option specifies a static memory buffer that SQLite can use for ** scratch memory. There are three arguments: A pointer an 8-byte ** aligned memory buffer from which the scratch allocations will be ** drawn, the size of each scratch allocation (sz), ** and the maximum number of scratch allocations (N). The sz @@ -1868,13 +1879,13 @@ ** ^SQLite will never require a scratch buffer that is more than 6 ** times the database page size. ^If SQLite needs needs additional ** scratch memory beyond what is provided by this configuration option, then ** [sqlite3_malloc()] will be used to obtain the memory needed.

SQLITE_CONFIG_PAGECACHE

^This option specifies a static memory buffer that SQLite can use for -** the database page cache with the default page cache implemenation. +** the database page cache with the default page cache implementation. ** This configuration should not be used if an application-define page ** cache implementation is loaded using the SQLITE_CONFIG_PCACHE option. ** There are three arguments to this option: A pointer to 8-byte aligned ** memory, the size of each page buffer (sz), and the number of pages (N). ** The sz argument should be the size of the largest database page @@ -1889,11 +1900,11 @@ ** SQLite goes to [sqlite3_malloc()] for the additional storage space. ** The pointer in the first argument must ** be aligned to an 8-byte boundary or subsequent behavior of SQLite ** will be undefined.

SQLITE_CONFIG_HEAP

^This option specifies a static memory buffer that SQLite will use ** for all of its dynamic memory allocation needs beyond those provided ** for by [SQLITE_CONFIG_SCRATCH] and [SQLITE_CONFIG_PAGECACHE]. ** There are three arguments: An 8-byte aligned pointer to the memory, ** the number of bytes in the memory buffer, and the minimum allocation size. @@ -1906,11 +1917,11 @@ ** The first pointer (the memory pointer) must be aligned to an 8-byte ** boundary or subsequent behavior of SQLite will be undefined. ** The minimum allocation size is capped at 2^12. Reasonable values ** for the minimum allocation size are 2^5 through 2^8.

SQLITE_CONFIG_MUTEX

^(This option takes a single argument which is a pointer to an ** instance of the [sqlite3_mutex_methods] structure. The argument specifies ** alternative low-level mutex routines to be used in place ** the mutex routines built into SQLite.)^ ^SQLite makes a copy of the ** content of the [sqlite3_mutex_methods] structure before the call to @@ -1918,11 +1929,11 @@ ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then ** the entire mutexing subsystem is omitted from the build and hence calls to ** [sqlite3_config()] with the SQLITE_CONFIG_MUTEX configuration option will ** return [SQLITE_ERROR].

SQLITE_CONFIG_GETMUTEX

^(This option takes a single argument which is a pointer to an ** instance of the [sqlite3_mutex_methods] structure. The ** [sqlite3_mutex_methods] ** structure is filled with the currently defined mutex routines.)^ ** This option can be used to overload the default mutex allocation @@ -1931,32 +1942,32 @@ ** the [SQLITE_THREADSAFE | SQLITE_THREADSAFE=0] compile-time option then ** the entire mutexing subsystem is omitted from the build and hence calls to ** [sqlite3_config()] with the SQLITE_CONFIG_GETMUTEX configuration option will ** return [SQLITE_ERROR].

SQLITE_CONFIG_LOOKASIDE

^(This option takes two arguments that determine the default ** memory allocation for the lookaside memory allocator on each ** [database connection]. The first argument is the ** size of each lookaside buffer slot and the second is the number of ** slots allocated to each database connection.)^ ^(This option sets the ** default lookaside size. The [SQLITE_DBCONFIG_LOOKASIDE] ** verb to [sqlite3_db_config()] can be used to change the lookaside ** configuration on individual connections.)^

SQLITE_CONFIG_PCACHE

^(This option takes a single argument which is a pointer to ** an [sqlite3_pcache_methods] object. This object specifies the interface ** to a custom page cache implementation.)^ ^SQLite makes a copy of the ** object and uses it for page cache memory allocations.

SQLITE_CONFIG_GETPCACHE

^(This option takes a single argument which is a pointer to an ** [sqlite3_pcache_methods] object. SQLite copies of the current ** page cache implementation into that object.)^

SQLITE_CONFIG_LOG

^The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a ** function with a call signature of void(*)(void*,int,const char*), ** and a pointer to void. ^If the function pointer is not NULL, it is ** invoked by [sqlite3_log()] to process each logging event. ^If the ** function pointer is NULL, the [sqlite3_log()] interface becomes a no-op. @@ -1970,10 +1981,22 @@ ** The SQLite logging interface is not reentrant; the logger function ** supplied by the application must not invoke any SQLite interface. ** In a multi-threaded application, the application-defined logger ** function must be threadsafe.

SQLITE_CONFIG_URI +**

This option takes a single argument of type int. If non-zero, then +** URI handling is globally enabled. If the parameter is zero, then URI handling +** is globally disabled. If URI handling is globally enabled, all filenames +** passed to [sqlite3_open()], [sqlite3_open_v2()], [sqlite3_open16()] or +** specified as part of [ATTACH] commands are interpreted as URIs, regardless +** of whether or not the [SQLITE_OPEN_URI] flag is set when the database +** connection is opened. If it is globally disabled, filenames are +** only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the +** database connection is opened. By default, URI handling is globally +** disabled. The default value may be changed by compiling with the +** [SQLITE_USE_URI] symbol defined. **

*/ #define SQLITE_CONFIG_SINGLETHREAD 1 /* nil */ #define SQLITE_CONFIG_MULTITHREAD 2 /* nil */ #define SQLITE_CONFIG_SERIALIZED 3 /* nil */ @@ -1988,10 +2011,11 @@ /* previously SQLITE_CONFIG_CHUNKALLOC 12 which is now unused. */ #define SQLITE_CONFIG_LOOKASIDE 13 /* int int */ #define SQLITE_CONFIG_PCACHE 14 /* sqlite3_pcache_methods* */ #define SQLITE_CONFIG_GETPCACHE 15 /* sqlite3_pcache_methods* */ #define SQLITE_CONFIG_LOG 16 /* xFunc, void* */ +#define SQLITE_CONFIG_URI 17 /* int */ /* ** CAPI3REF: Database Connection Configuration Options ** ** These constants are the available integer configuration options that @@ -2073,17 +2097,21 @@ ** the table has a column of type [INTEGER PRIMARY KEY] then that column ** is another alias for the rowid. ** ** ^This routine returns the [rowid] of the most recent ** successful [INSERT] into the database from the [database connection] -** in the first argument. ^If no successful [INSERT]s +** in the first argument. ^As of SQLite version 3.7.7, this routines +** records the last insert rowid of both ordinary tables and [virtual tables]. +** ^If no successful [INSERT]s ** have ever occurred on that database connection, zero is returned. ** -** ^(If an [INSERT] occurs within a trigger, then the [rowid] of the inserted -** row is returned by this routine as long as the trigger is running. -** But once the trigger terminates, the value returned by this routine -** reverts to the last value inserted before the trigger fired.)^ +** ^(If an [INSERT] occurs within a trigger or within a [virtual table] +** method, then this routine will return the [rowid] of the inserted +** row as long as the trigger or virtual table method is running. +** But once the trigger or virtual table method ends, the value returned +** by this routine reverts to what it was before the trigger or virtual +** table method began.)^ ** ** ^An [INSERT] that fails due to a constraint violation is not a ** successful [INSERT] and does not change the value returned by this ** routine. ^Thus INSERT OR FAIL, INSERT OR IGNORE, INSERT OR ROLLBACK, ** and INSERT OR ABORT make no changes to the return value of this @@ -2742,10 +2770,13 @@ ** The [sqlite3_set_authorizer | authorizer callback function] must ** return either [SQLITE_OK] or one of these two constants in order ** to signal SQLite whether or not the action is permitted. See the ** [sqlite3_set_authorizer | authorizer documentation] for additional ** information. +** +** Note that SQLITE_IGNORE is also used as a [SQLITE_ROLLBACK | return code] +** from the [sqlite3_vtab_on_conflict()] interface. */ #define SQLITE_DENY 1 /* Abort the SQL statement with an error */ #define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */ /* @@ -2864,11 +2895,11 @@ SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*); /* ** CAPI3REF: Opening A New Database Connection ** -** ^These routines open an SQLite database file whose name is given by the +** ^These routines open an SQLite database file as specified by the ** filename argument. ^The filename argument is interpreted as UTF-8 for ** sqlite3_open() and sqlite3_open_v2() and as UTF-16 in the native byte ** order for sqlite3_open16(). ^(A [database connection] handle is usually ** returned in *ppDb, even if an error occurs. The only exception is that ** if SQLite is unable to allocate memory to hold the [sqlite3] object, @@ -2891,11 +2922,11 @@ ** except that it accepts two additional parameters for additional control ** over the new database connection. ^(The flags parameter to ** sqlite3_open_v2() can take one of ** the following three values, optionally combined with the ** [SQLITE_OPEN_NOMUTEX], [SQLITE_OPEN_FULLMUTEX], [SQLITE_OPEN_SHAREDCACHE], -** and/or [SQLITE_OPEN_PRIVATECACHE] flags:)^ +** [SQLITE_OPEN_PRIVATECACHE], and/or [SQLITE_OPEN_URI] flags:)^ ** **

[SQLITE_OPEN_READONLY]: The database is opened in read-only mode. If the database does not ** already exist, an error is returned.

** ** If the 3rd parameter to sqlite3_open_v2() is not one of the -** combinations shown above or one of the combinations shown above combined -** with the [SQLITE_OPEN_NOMUTEX], [SQLITE_OPEN_FULLMUTEX], -** [SQLITE_OPEN_SHAREDCACHE] and/or [SQLITE_OPEN_PRIVATECACHE] flags, +** combinations shown above optionally combined with other +** [SQLITE_OPEN_READONLY | SQLITE_OPEN_* bits] ** then the behavior is undefined. ** ** ^If the [SQLITE_OPEN_NOMUTEX] flag is set, then the database connection ** opens in the multi-thread [threading mode] as long as the single-thread ** mode has not been set at compile-time or start-time. ^If the @@ -2926,10 +2956,15 @@ ** ^The [SQLITE_OPEN_SHAREDCACHE] flag causes the database connection to be ** eligible to use [shared cache mode], regardless of whether or not shared ** cache is enabled using [sqlite3_enable_shared_cache()]. ^The ** [SQLITE_OPEN_PRIVATECACHE] flag causes the database connection to not ** participate in [shared cache mode] even if it is enabled. +** +** ^The fourth parameter to sqlite3_open_v2() is the name of the +** [sqlite3_vfs] object that defines the operating system interface that +** the new database connection should use. ^If the fourth parameter is +** a NULL pointer then the default [sqlite3_vfs] object is used. ** ** ^If the filename is ":memory:", then a private, temporary in-memory database ** is created for the connection. ^This in-memory database will vanish when ** the database connection is closed. Future versions of SQLite might ** make use of additional special filenames that begin with the ":" character. @@ -2939,14 +2974,115 @@ ** ** ^If the filename is an empty string, then a private, temporary ** on-disk database will be created. ^This private database will be ** automatically deleted as soon as the database connection is closed. ** -** ^The fourth parameter to sqlite3_open_v2() is the name of the -** [sqlite3_vfs] object that defines the operating system interface that -** the new database connection should use. ^If the fourth parameter is -** a NULL pointer then the default [sqlite3_vfs] object is used. +** [[URI filenames in sqlite3_open()]]

URI Filenames

+** +** ^If [URI filename] interpretation is enabled, and the filename argument +** begins with "file:", then the filename is interpreted as a URI. ^URI +** filename interpretation is enabled if the [SQLITE_OPEN_URI] flag is +** set in the fourth argument to sqlite3_open_v2(), or if it has +** been enabled globally using the [SQLITE_CONFIG_URI] option with the +** [sqlite3_config()] method or by the [SQLITE_USE_URI] compile-time option. +** As of SQLite version 3.7.7, URI filename interpretation is turned off +** by default, but future releases of SQLite might enable URI filename +** interpretation by default. See "[URI filenames]" for additional +** information. +** +** URI filenames are parsed according to RFC 3986. ^If the URI contains an +** authority, then it must be either an empty string or the string +** "localhost". ^If the authority is not an empty string or "localhost", an +** error is returned to the caller. ^The fragment component of a URI, if +** present, is ignored. +** +** ^SQLite uses the path component of the URI as the name of the disk file +** which contains the database. ^If the path begins with a '/' character, +** then it is interpreted as an absolute path. ^If the path does not begin +** with a '/' (meaning that the authority section is omitted from the URI) +** then the path is interpreted as a relative path. +** ^On windows, the first component of an absolute path +** is a drive specification (e.g. "C:"). +** +** [[core URI query parameters]] +** The query component of a URI may contain parameters that are interpreted +** either by SQLite itself, or by a [VFS | custom VFS implementation]. +** SQLite interprets the following three query parameters: +** +**

vfs: ^The "vfs" parameter may be used to specify the name of +** a VFS object that provides the operating system interface that should +** be used to access the database file on disk. ^If this option is set to +** an empty string the default VFS object is used. ^Specifying an unknown +** VFS is an error. ^If sqlite3_open_v2() is used and the vfs option is +** present, then the VFS specified by the option takes precedence over +** the value passed as the fourth parameter to sqlite3_open_v2(). +** +**
mode: ^(The mode parameter may be set to either "ro", "rw" or +** "rwc". Attempting to set it to any other value is an error)^. +** ^If "ro" is specified, then the database is opened for read-only +** access, just as if the [SQLITE_OPEN_READONLY] flag had been set in the +** third argument to sqlite3_prepare_v2(). ^If the mode option is set to +** "rw", then the database is opened for read-write (but not create) +** access, as if SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had +** been set. ^Value "rwc" is equivalent to setting both +** SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE. ^If sqlite3_open_v2() is +** used, it is an error to specify a value for the mode parameter that is +** less restrictive than that specified by the flags passed as the third +** parameter. +** +**
cache: ^The cache parameter may be set to either "shared" or +** "private". ^Setting it to "shared" is equivalent to setting the +** SQLITE_OPEN_SHAREDCACHE bit in the flags argument passed to +** sqlite3_open_v2(). ^Setting the cache parameter to "private" is +** equivalent to setting the SQLITE_OPEN_PRIVATECACHE bit. +** ^If sqlite3_open_v2() is used and the "cache" parameter is present in +** a URI filename, its value overrides any behaviour requested by setting +** SQLITE_OPEN_PRIVATECACHE or SQLITE_OPEN_SHAREDCACHE flag. +**

+** +** ^Specifying an unknown parameter in the query component of a URI is not an +** error. Future versions of SQLite might understand additional query +** parameters. See "[query parameters with special meaning to SQLite]" for +** additional information. +** +** [[URI filename examples]]

URI filename examples

+** +** +**

URI filenames	Results +**
file:data.db	+ Open the file "data.db" in the current directory. +
file:/home/fred/data.db + file:///home/fred/data.db + file://localhost/home/fred/data.db	+ Open the database file "/home/fred/data.db". +
file://darkstar/home/fred/data.db	+ An error. "darkstar" is not a recognized authority. +
+ file:///C:/Documents%20and%20Settings/fred/Desktop/data.db +	Windows only: Open the file "data.db" on fred's desktop on drive + C:. Note that the %20 escaping in this example is not strictly + necessary - space characters can be used literally + in URI filenames. +
file:data.db?mode=ro&cache=private	+ Open file "data.db" in the current directory for read-only access. + Regardless of whether or not shared-cache mode is enabled by + default, use a private cache. +
file:/home/fred/data.db?vfs=unix-nolock	+ Open file "/home/fred/data.db". Use the special VFS "unix-nolock". +
file:data.db?mode=readonly	+ An error. "readonly" is not a valid option for the "mode" parameter. +

+** +** ^URI hexadecimal escape sequences (%HH) are supported within the path and +** query components of a URI. A hexadecimal escape sequence consists of a +** percent sign - "%" - followed by exactly two hexadecimal digits +** specifying an octet value. ^Before the path or query components of a +** URI filename are interpreted, they are encoded using UTF-8 and all +** hexadecimal escape sequences replaced by a single byte containing the +** corresponding octet. If this process generates an invalid UTF-8 encoding, +** the results are undefined. ** ** Note to Windows users: The encoding used for the filename argument ** of sqlite3_open() and sqlite3_open_v2() must be UTF-8, not whatever ** codepage is currently defined. Filenames containing international ** characters must be converted to UTF-8 prior to passing them into @@ -2964,10 +3100,30 @@ const char *filename, /* Database filename (UTF-8) */ sqlite3 **ppDb, /* OUT: SQLite db handle */ int flags, /* Flags */ const char *zVfs /* Name of VFS module to use */ ); + +/* +** CAPI3REF: Obtain Values For URI Parameters +** +** This is a utility routine, useful to VFS implementations, that checks +** to see if a database file was a URI that contained a specific query +** parameter, and if so obtains the value of the query parameter. +** +** The zFilename argument is the filename pointer passed into the xOpen() +** method of a VFS implementation. The zParam argument is the name of the +** query parameter we seek. This routine returns the value of the zParam +** parameter if it exists. If the parameter does not exist, this routine +** returns a NULL pointer. +** +** If the zFilename argument to this function is not a pointer that SQLite +** passed into the xOpen VFS method, then the behavior of this routine +** is undefined and probably undesirable. +*/ +SQLITE_API const char *sqlite3_uri_parameter(const char *zFilename, const char *zParam); + /* ** CAPI3REF: Error Codes And Messages ** ** ^The sqlite3_errcode() interface returns the numeric [result code] or @@ -3080,47 +3236,49 @@ ** that can be lowered at run-time using [sqlite3_limit()]. ** The synopsis of the meanings of the various limits is shown below. ** Additional information is available at [limits | Limits in SQLite]. ** **

SQLITE_LIMIT_LENGTH
SQLITE_LIMIT_LENGTH: The maximum size of any string or BLOB or table row, in bytes.; )^ ** -** ^(
SQLITE_LIMIT_SQL_LENGTH
SQLITE_LIMIT_SQL_LENGTH: The maximum length of an SQL statement, in bytes.
SQLITE_LIMIT_COLUMN
SQLITE_LIMIT_COLUMN: The maximum number of columns in a table definition or in the ** result set of a [SELECT] or the maximum number of columns in an index ** or in an ORDER BY or GROUP BY clause.
SQLITE_LIMIT_EXPR_DEPTH
SQLITE_LIMIT_EXPR_DEPTH: The maximum depth of the parse tree on any expression.
SQLITE_LIMIT_COMPOUND_SELECT
SQLITE_LIMIT_COMPOUND_SELECT: The maximum number of terms in a compound SELECT statement.
SQLITE_LIMIT_VDBE_OP
SQLITE_LIMIT_VDBE_OP: The maximum number of instructions in a virtual machine program ** used to implement an SQL statement. This limit is not currently ** enforced, though that might be added in some future release of ** SQLite.
SQLITE_LIMIT_FUNCTION_ARG
SQLITE_LIMIT_FUNCTION_ARG: The maximum number of arguments on a function.
SQLITE_LIMIT_ATTACHED
SQLITE_LIMIT_ATTACHED: The maximum number of [ATTACH | attached databases].)^
SQLITE_LIMIT_LIKE_PATTERN_LENGTH: The maximum length of the pattern argument to the [LIKE] or ** [GLOB] operators.
SQLITE_LIMIT_VARIABLE_NUMBER: The maximum index number of any [parameter] in an SQL statement.)^ ** -** ^(
SQLITE_LIMIT_TRIGGER_DEPTH
SQLITE_LIMIT_TRIGGER_DEPTH: The maximum depth of recursion for triggers.

SQLITE_STATUS_MEMORY_USED
SQLITE_STATUS_MEMORY_USED: This parameter is the current amount of memory checked out ** using [sqlite3_malloc()], either directly or indirectly. The ** figure includes calls made to [sqlite3_malloc()] by the application ** and internal memory usage by the SQLite library. Scratch memory ** controlled by [SQLITE_CONFIG_SCRATCH] and auxiliary page-cache ** memory controlled by [SQLITE_CONFIG_PAGECACHE] is not included in ** this parameter. The amount returned is the sum of the allocation ** sizes as reported by the xSize method in [sqlite3_mem_methods].
SQLITE_STATUS_MALLOC_SIZE
SQLITE_STATUS_MALLOC_SIZE: This parameter records the largest memory allocation request ** handed to [sqlite3_malloc()] or [sqlite3_realloc()] (or their ** internal equivalents). Only the value returned in the ** *pHighwater parameter to [sqlite3_status()] is of interest. ** The value written into the *pCurrent parameter is undefined.
SQLITE_STATUS_MALLOC_COUNT
SQLITE_STATUS_MALLOC_COUNT: This parameter records the number of separate memory allocations ** currently checked out.
SQLITE_STATUS_PAGECACHE_USED
SQLITE_STATUS_PAGECACHE_USED: This parameter returns the number of pages used out of the ** [pagecache memory allocator] that was configured using ** [SQLITE_CONFIG_PAGECACHE]. The ** value returned is in pages, not in bytes.
SQLITE_STATUS_PAGECACHE_OVERFLOW: This parameter returns the number of bytes of page cache ** allocation which could not be satisfied by the [SQLITE_CONFIG_PAGECACHE] ** buffer and where forced to overflow to [sqlite3_malloc()]. The ** returned value includes allocations that overflowed because they ** where too large (they were larger than the "sz" parameter to ** [SQLITE_CONFIG_PAGECACHE]) and allocations that overflowed because ** no space was left in the page cache.
SQLITE_STATUS_PAGECACHE_SIZE
SQLITE_STATUS_PAGECACHE_SIZE: This parameter records the largest memory allocation request ** handed to [pagecache memory allocator]. Only the value returned in the ** *pHighwater parameter to [sqlite3_status()] is of interest. ** The value written into the *pCurrent parameter is undefined.
SQLITE_STATUS_SCRATCH_USED
SQLITE_STATUS_SCRATCH_USED: This parameter returns the number of allocations used out of the ** [scratch memory allocator] configured using ** [SQLITE_CONFIG_SCRATCH]. The value returned is in allocations, not ** in bytes. Since a single thread may only have one scratch allocation ** outstanding at time, this parameter also reports the number of threads ** using scratch memory at the same time.
SQLITE_STATUS_SCRATCH_OVERFLOW
SQLITE_STATUS_SCRATCH_OVERFLOW: This parameter returns the number of bytes of scratch memory ** allocation which could not be satisfied by the [SQLITE_CONFIG_SCRATCH] ** buffer and where forced to overflow to [sqlite3_malloc()]. The values ** returned include overflows because the requested allocation was too ** larger (that is, because the requested allocation was larger than the ** "sz" parameter to [SQLITE_CONFIG_SCRATCH]) and because no scratch buffer ** slots were available. **
SQLITE_STATUS_SCRATCH_SIZE
SQLITE_STATUS_SCRATCH_SIZE: This parameter records the largest memory allocation request ** handed to [scratch memory allocator]. Only the value returned in the ** *pHighwater parameter to [sqlite3_status()] is of interest. ** The value written into the *pCurrent parameter is undefined.
SQLITE_STATUS_PARSER_STACK
SQLITE_STATUS_PARSER_STACK: This parameter records the deepest parser stack. It is only ** meaningful if SQLite is compiled with [YYTRACKMAXSTACKDEPTH].

** ** New status parameters may be added from time to time. @@ -6088,13 +6254,13 @@ ** ** ^This interface is used to retrieve runtime status information ** about a single [database connection]. ^The first argument is the ** database connection object to be interrogated. ^The second argument ** is an integer constant, taken from the set of -** [SQLITE_DBSTATUS_LOOKASIDE_USED | SQLITE_DBSTATUS_*] macros, that +** [SQLITE_DBSTATUS options], that ** determines the parameter to interrogate. The set of -** [SQLITE_DBSTATUS_LOOKASIDE_USED | SQLITE_DBSTATUS_*] macros is likely +** [SQLITE_DBSTATUS options] is likely ** to grow in future releases of SQLite. ** ** ^The current value of the requested parameter is written into *pCur ** and the highest instantaneous value is written into *pHiwtr. ^If ** the resetFlg is true, then the highest instantaneous value is @@ -6107,10 +6273,11 @@ */ SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int resetFlg); /* ** CAPI3REF: Status Parameters for database connections +** KEYWORDS: {SQLITE_DBSTATUS options} ** ** These constants are the available integer "verbs" that can be passed as ** the second argument to the [sqlite3_db_status()] interface. ** ** New verbs may be added in future releases of SQLite. Existing verbs @@ -6118,48 +6285,50 @@ ** [sqlite3_db_status()] to make sure that the call worked. ** The [sqlite3_db_status()] interface will return a non-zero error code ** if a discontinued or unsupported verb is invoked. ** **

SQLITE_DBSTATUS_LOOKASIDE_USED
SQLITE_DBSTATUS_LOOKASIDE_USED: This parameter returns the number of lookaside memory slots currently ** checked out.
SQLITE_DBSTATUS_LOOKASIDE_HIT
SQLITE_DBSTATUS_LOOKASIDE_HIT: This parameter returns the number malloc attempts that were ** satisfied using lookaside memory. Only the high-water value is meaningful; ** the current value is always zero.)^ ** +** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE]] ** ^(
SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE: This parameter returns the number malloc attempts that might have ** been satisfied using lookaside memory but failed due to the amount of ** memory requested being larger than the lookaside slot size. ** Only the high-water value is meaningful; ** the current value is always zero.)^ ** +** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL]] ** ^(
SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL: This parameter returns the number malloc attempts that might have ** been satisfied using lookaside memory but failed due to all lookaside ** memory already being in use. ** Only the high-water value is meaningful; ** the current value is always zero.)^ ** -** ^(
SQLITE_DBSTATUS_CACHE_USED
SQLITE_DBSTATUS_CACHE_USED: This parameter returns the approximate number of of bytes of heap ** memory used by all pager caches associated with the database connection.)^ ** ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_USED is always 0. ** -** ^(
SQLITE_DBSTATUS_SCHEMA_USED
SQLITE_DBSTATUS_SCHEMA_USED: This parameter returns the approximate number of of bytes of heap ** memory used to store the schema for all databases associated ** with the connection - main, temp, and any [ATTACH]-ed databases.)^ ** ^The full amount of memory used by the schemas is reported, even if the ** schema memory is shared with other database connections due to ** [shared cache mode] being enabled. ** ^The highwater mark associated with SQLITE_DBSTATUS_SCHEMA_USED is always 0. ** -** ^(
SQLITE_DBSTATUS_STMT_USED
SQLITE_DBSTATUS_STMT_USED: This parameter returns the approximate number of of bytes of heap ** and lookaside memory used by all prepared statements associated with ** the database connection.)^ ** ^The highwater mark associated with SQLITE_DBSTATUS_STMT_USED is always 0. **

- This is a fork of the popular ADO.NET 2.0 adaptor for SQLite known - as System.Data.SQLite. The originator of System.Data.SQLite, Robert Simpson, - is aware of this fork, has expressed his approval, and has commit privileges on the new Fossil repository. - The SQLite development team intends to maintain System.Data.SQLite moving forward. + This is a fork of the popular ADO.NET adapter for + SQLite known as System.Data.SQLite. The + originator of System.Data.SQLite, Robert Simpson, is aware of this fork, has + expressed his approval, and has commit privileges on the new Fossil + repository. The SQLite development team intends to maintain + System.Data.SQLite moving forward.

- Historical versions, as well as the original support forums, may still be found - at http://sqlite.phxsoftware.com, though - there have been no updates to this version since April of 2010. + Historical versions, as well as the original support forums, may still be + found at http://sqlite.phxsoftware.com/, + though there have been no updates to this version since April of 2010.

Index: www/news.wiki ================================================================== --- www/news.wiki +++ www/news.wiki @@ -1,9 +1,28 @@ News Version History +

+ 1.0.74.0 - July 4, 2011 +

Updated to SQLite 3.7.7.1 [af0d91adf4].
Fix incorrect hard-coded .NET Framework version information SQLiteFactory_Linq.cs that was causing IServiceProvider.GetService to fail when running against the .NET Framework 3.5.
Fix all XML documentation warnings.
Restore support for the mixed-mode assembly (i.e. the one that can be registered in the Global Assembly Cache).
Restore support for the Compact Framework.
Remove unused "using" statements from the System.Data.SQLite and System.Data.SQLite.Linq projects.
Remove hard-coded System.Data.SQLite.Linq version from SQLiteFactory_Linq.cs
Modify the setup to support bundled packages (i.e. with the mixed-mode assembly) and standard packages (i.e. with the managed assembly separate from the native interop library).
Disable the ability to register with the Global Assembly Cache in the standard setup package (i.e. it is available in the bundled setup only).
Remove PATH modification from the setup.
Modify the naming scheme for the source, setup, and binary packages to allow for the necessary variants.
In the build automation, attempt to automatically detect if Visual Studio 2008 and/or 2010 are installed and support building binaries for both at once, when available.
Add release automation to build the source, setup, and binary packages in all supported build variants.
Add the testlinq project to the new build system and make it work properly with Visual Studio 2008 and 2010.

1.0.73.0 - June 2, 2011

Updated to SQLite 3.7.6.3 [ed1da510a2].

Release Procedures

This content on this page is outdated and needs to be updated.

Follow these steps to prepare a new release of System.Data.SQLite. Unless otherwise noted, all steps need to be done in the order specified.

URI Filenames

URI filename examples

URI Filenames

URI filename examples

Build Procedures

Build Assumptions

Build Procedures

Build Assumptions & Prerequisites

All Builds

Manual Build

Automated Build

build.bat Desription

SQLite Download Page

System.Data.SQLite Download Page

Build Product Names

Canonical Source Code

Features

[H1 Header]

- [Sub Section]

Version History

About SQLite.NET

SQLite.NET Provider Features

Distributing the Binaries (Compact Framework)

Release Procedures