The engine is acid compliant to the full SQL96 standard and offers built in strong encryption as well as many other features. It’s also well catered for in extensions, where for example it can use the ‘Spatialite’ extension to provide GIS features, usually only found in larger databases such as Postgres. Installing it into your application is as simple as searching for it on NuGet and hitting install programming it is done using plain ADO.Net with ‘SQLite’ being the object prefix, EG: ‘SQLiteConnection’ or ‘SQLiteDataReader’ or using the entity framework bindings to use it as part of the EF-Orm.
Originally written as a C based unmanaged library, it now has managed bindings that call an un-managed stub (Usually called SqliteInterop.dll), which means it can be used with both un-managed and managed applications on the Windows platform.
It’s supported on Classic Windows Mobile, Windows CE, Windows Phone, Android, iOS, Linux, Windows, Unix and just about every other platform I’ve ever used. The best part about SQLite is how cross platform it is. NET for a few years now, and supports not only plain old ADO.NET but in recent versions, entity framework too. What’s not to love about the world’s favourite portable database, SQLite is not only super portable (Requires 2 or 3 Dll’s) and is extremely fast. Whatever your point of view the data is essentially portable in some form. This week’s post is going to take a quick look at what’s available out there, and a few of the pros and cons of each.īefore I get started though, I will be mentioning a couple of data stores that are not truly portable here, but in my mind I think they qualify because even though they are not as portable as some, they are almost zero configuration, and easy to wrap up with your application (besides the term portable is quite subjective to some portable means being able to pick up the database file and hand it around, to others being portable just means the database stays with the device).
NET has no shortage of, it’s small scale offerings that fill this gap just nicely. In some cases, it’s even a requirement for a server based system, where for various reasons you may not be able to install a full scale DBMS such as SqlServer or Postgres or some other heavy iron stand alone system. In today’s world of mobile apps, it’s not an unreasonable expectation to want a database that’s small, lightweight, and travels with the app from device to device.
0 kommentar(er)
