4 ms·
Of course I would opt for Sqlite, however if I really need NoSQL type of data I always would recommend LiteDB. The API is similar to MongoDB which is great bec
by romanovcode 9y ago
Of course I would opt for Sqlite, however if I really need NoSQL type of data I always would recommend LiteDB.
The API is similar to MongoDB which is great because I consider MongoDB drivers the best DB drivers for C# except for maybe EF.
- SonicSoul 9y agocan you elaborate on opting for Sqllite?
- cbcoutinho 9y agoSqlite is one of the simplest RDBMSs that you can run on a client, which is really useful for deploying apps that need their own data store
- romanovcode 9y agoAlso Sqlite has native EF drivers which makes it first-class .NET citizen.
- deleted 9y ago[deleted]
- j_s 9y agoBattle-tested multiplatform support (and thus reliability) is definitely a key selling point. This is further reinforced by its impressively extensive test suite. Long ago I lost my first Android smartphone's SMS database since they used to delete + re-create even barely corrupted databases, but by now most of the kinks have been worked out.
- sametmax 9y agoPlus it's amazingly fast and is packed with SQL features. For such a small lib, it's a miracle. And the way the author talks about it (he is not from a DB background) it so funny.
- j_s 9y agoIs it possible to pre-allocate a fixed-size file with sqlite to then use as a local cache evicting old data? Supporting this may offer a chance to differentiate a bit. Closest I could find was a workaround that is probably close enough (disable auto_vacuum and delete a giant blob) https://stackoverflow.com/a/4821318 https://stackoverflow.com/a/4821318.