map_suite_sqlite_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
map_suite_sqlite_guide [2015/09/16 09:55] admin [Editing Records] |
map_suite_sqlite_guide [2015/09/16 10:00] (current) admin [SQLite Dependencies] |
||
|---|---|---|---|
| Line 60: | Line 60: | ||
| ==== Deleting Records ==== | ==== Deleting Records ==== | ||
| <code csharp> | <code csharp> | ||
| - | <nowiki>//</nowiki> Here we are deleting features 1 and 2. | + | // Here we are deleting features 1 and 2. |
| sqliteFeatureSource.BeginTransaction(); | sqliteFeatureSource.BeginTransaction(); | ||
| sqliteFeatureSource.DeleteFeature("1"); | sqliteFeatureSource.DeleteFeature("1"); | ||
| Line 69: | Line 69: | ||
| ==== Opening a SQLiteFeatureLayer For Display or Analysis ==== | ==== Opening a SQLiteFeatureLayer For Display or Analysis ==== | ||
| <code csharp> | <code csharp> | ||
| - | <nowiki>//</nowiki> We open the FeatureLayer and pass in the database path along with the table name, id column and geometry column. | + | // We open the FeatureLayer and pass in the database path along with the table name, id column and geometry column. |
| SqliteFeatureLayer sqliteFeatureLayer = new SqliteFeatureLayer(@"Data Source=C:\sampledata\austin_streets.sqlite;Version=3;", "austin_streets", "id", "geometry"); | SqliteFeatureLayer sqliteFeatureLayer = new SqliteFeatureLayer(@"Data Source=C:\sampledata\austin_streets.sqlite;Version=3;", "austin_streets", "id", "geometry"); | ||
| sqliteFeatureLayer.Open(); | sqliteFeatureLayer.Open(); | ||
| Line 138: | Line 138: | ||
| ===== SQLite Dependencies ===== | ===== SQLite Dependencies ===== | ||
| - | We use the unmanaged implementation of SQLite provided by the creators via a NuGet package. Specifically, we use the package ‘System.Data.SQLite Core (x86/x64)’ because it has no other dependencies and supports both 32 and 64 bit application. When you add a reference to our SQLiteExtension, it will require you to add a reference to this NuGet package from your main application so that the unmanaged assemblies are included in the bin. As they are copied to the bin we support x-copy deployment and avoid potential conflict with other instances of SQLite that may exist on the machine. The specific package we use is the {{Is there a missing word here?|error}} It is currently not suitable for a fully managed deployment. If you have such an application, please let us know and we can consider another approach for your specific project. | + | We use the unmanaged implementation of SQLite provided by the creators via a NuGet package. Specifically, we use the package ‘System.Data.SQLite Core (x86/x64)’ because it has no other dependencies and supports both 32 and 64 bit application. When you add a reference to our SQLiteExtension, it will require you to add a reference to this NuGet package from your main application so that the unmanaged assemblies are included in the bin. As they are copied to the bin we support x-copy deployment and avoid potential conflict with other instances of SQLite that may exist on the machine. The specific package we use is the [[Is there a missing word here?|Template:Is there a missing word here? ]] It is currently not suitable for a fully managed deployment. If you have such an application, please let us know and we can consider another approach for your specific project. |
| https://www.nuget.org/packages/System.Data.SQLite.Core/ | https://www.nuget.org/packages/System.Data.SQLite.Core/ | ||
map_suite_sqlite_guide.1442397356.txt.gz · Last modified: 2015/09/16 09:55 by admin