Basic connection string used to connect to the SQLite database.
1: 2: 3: 4: 5:
Path to search for database vendor speficic assemblies. Specify the path where
System.Data.SQLite.dll is stored.
If you use the System.Data.SQLite NuGet package and target .NET 4.6, the path would be something like
__SOURCE_DIRECTORY__ + @"\..\packages\System.Data.SQLite.Core.<version>\lib\net46".
Both absolute and relative paths are supported.
System.Data.SQLite.dll will look for the native interop library:
- on Windows:
x86subdirectories of the resolution path.
- on Linux:
libSQLite.Interop.soin the resolution path directory.
The interop libraries are not properly placed afer the System.Data.SQLite NuGet package is added, so you might have to manually copy the interop libraries:
on Windows: copy
x86subdirectories from SQLite build directory, which typically is
- on Linux: first build the
<srcDir>/Setup/compile-interop-assembly-release.shscript from System.Data.SQLite source distribution
sqlite-netFx-source-1.x.xxx.x.zip. And then copy it from
System.Data.SQLite.dll is in the location where NuGet places it by default, you don't have to submit
the ResolutionPath parameter at all, but you still need to copy the interop libraries as described above.
If you use Microsoft.Data.Sqlite driver, you still need the physical dll, (in that case e_sqlite3.dll), to be in resolutionPath or folder under operating system PATH variable.
Specifies what SQLite library to use. This is an
SQLiteLibrary enumeration, defined in the
namespace, which has the following members:
AutoSelect- Uses System.Data.SQLite under .NET, Mono.Data.SQLite under Mono and Microsoft.Data.Sqlite under NET Core. This is the default.
MonoDataSQLite- Always uses Mono.Data.SQLite.
SystemDataSQLite- Always uses System.Data.SQLite.
MicrosoftDataSqlite- Always uses Microsoft.Data.Sqlite. This is experimental until it supports GetSchema().
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13:
When you do insert operation, after .SubmitUpdates call you can get inserted rowid like this:
1: 2: 3: