Index: Doc/Extra/dbfactorysupport.html ================================================================== --- Doc/Extra/dbfactorysupport.html +++ Doc/Extra/dbfactorysupport.html @@ -63,11 +63,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.28.0, Culture=neutral, + Version=1.0.29.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139"/> </DbProviderFactories> </system.data> </configuration> Index: Doc/Extra/limitations.html ================================================================== --- Doc/Extra/limitations.html +++ Doc/Extra/limitations.html @@ -22,13 +22,11 @@
As providers go, this one doesn't have many restrictions. SQLite has no - support for row-level or table-level locks. Therefore when a DataReader is - active the database cannot be written to, and when the database is open for - writing no DataReaders can be open. The SQLite.NET provider attempts to retry + support for row-level or table-level locks. When a connection locks the database for writing, no other connection or process may read or write to the database until the write operation is complete. The SQLite.NET provider attempts to retry internally if a database is locked, up to the CommandTimeout property of the command in question.
SQLite is inherently type-less, and only understands a few basic datatypes natively. They are (in .NET-speak) Int64, Double, String and Blob. The SQLite.NET provider will use the database schema information it can glean to Index: Doc/Extra/version.html ================================================================== --- Doc/Extra/version.html +++ Doc/Extra/version.html @@ -21,10 +21,17 @@
1.0.29.0 - May 16, 2006
+1.0.28.0 - April 14, 2006