Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I have the following scenario. I need a db to store XML messages that have been created by a reader. I then want to use a transport (wcf) to read the db external to the populating app and send the messages to a central db Generally the db needs to run on mono, and windows.
I did look at sqlite3, and it seemed to fit all my requirements, but i'm reading its not so good on multi process access and t's moving away from my sweet spot, these last couple of days.
Thanks.
Have you considered just using XML to store the data? It doesn't get any more portable than that and will work fine as long your client-side storage needs are simple. E.g. not a large amount of many domain objects that need to be stored.
Additionally using an XML data store solves a lot of setup and installation headaches. You simply reference a file (or files) relative to your executable. You don't need to worry about installing db engines for a variety of platforms and then worry about upgrading.
WOuld it be feasible to give each process their own sqlite3 database? They all ultimately use the central database anyway, right?
Have a look at Firebird.
You can use it as an embedded engine just like SQLite, but it can scale to a full blown server as well.
The only drawback is, that the documentation is a mess
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I was wonder if there any alternative way to store offline data in dependencies database rather than using sqflite!!
if any one knows any SQL or even nosql libraries for flutter that's is not complicated like sqflite please mention it!
This is a alternative, use a NoSql database.
Sembast
Yet another NoSQL persistent store database solution for single process io applications. The whole document based database resides in a single file and is loaded in memory when opened. Changes are appended right away to the file and the file is automatically compacted when needed.
Works on Dart VM and Flutter (no plugin needed, 100% Dart). Inspired from IndexedDB, DataStore, WebSql, NeDB, Lawndart...
Supports encryption using user-defined codec.
This is a link when you can get the library:
https://pub.dev/packages/sembast
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I am using redis to store highly requested info, but I want to store less-requested stuff in a list/set on the disk. I have been looking around with no luck. Memcached, Riak etc. don't seem to have list/set datatypes. Is there a database that have those features?
Thanks.
Run another Redis instance and configure it with AOF on. Append-only file.
You can read more about it here:
http://redis.io/topics/persistence
Scroll half way down, there is alot of good information on it.
Append-only file
Snapshotting is not very durable. If your computer
running Redis stops, your power line fails, or you accidentally kill
-9 your instance, the latest data written on Redis will get lost. While this may not be a big deal for some applications, there are use
cases for full durability, and in these cases Redis was not a viable
option. The append-only file is an alternative, fully-durable strategy
for Redis. It became available in version 1.1. You can turn on the AOF
in your configuration file: appendonly yes From now on, every time
Redis receives a command that changes the dataset (e.g. SET) it will
append it to the AOF. When you restart Redis it will re-play the AOF
to rebuild the state.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I would like to move some users off of MS Access and onto an open-source DB like MySQL, Postegres, or even SQLite. Transferring the tables from one DB to another is no problem, but I need to be able to also provide them with a similar UI as the MS Access forms they are using to input the data. Additionally, I would like to be able to give them nice report outputs that reference a table or query.
What open-source alternatives are suggested/available for easily building and storing queries, forms, and reports similar to MS Access, without a ton of programming needed to get them up-and-running quickly?
Obviously I am immediately targeting Windows alternatives, but I don't want to limit suggestions to just one OS.
Open Office - Base seems to be a good option
We were to solve this problem also and considered OO Base not being very good option (note it was like 4 years ago). So we use MS Access as a frontend with ODBC connection to mysql database. It works quite well.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I'm looking for a solution to add persistence to my native-code application. It should be simple (no SQL), fast, and most-importantly reliable.
The best approach I can think of is using memory-mapped files. It's as simple and fast as it can get - you simply store the values in plain-data arrays in "memory". However, I don't think it's very reliable - a power failure could leave the database in an inconsistent or corrupted state. Being able to transactionally sync a group of memory-mapped files to disk would solve this, but I don't think it's possible. Also, unless the filesystem supports snapshots or COW cloning (e.g. Brtfs), backups would mean having to stop the application completely while the files are being copied.
Does anyone have better ideas?
Tokyo Cabinet
http://fallabs.com/tokyocabinet/
Berkeley DB
http://www.oracle.com/technetwork/database/berkeleydb/overview/index.html
Your list of requirements sounds like Redis. See http://redis.io/ for more.
Another possibility is Cassandra. See http://cassandra.apache.org/ for more on that.
RocksDB or levelDB are other great options.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I need open source database that I can ship with my commercial application.
It should not have any installation (i.e., no window service and no setup).
It can be single user database. It should work in Windows environment and used from Java code.
Thanks
I really like SQLite. You can use it with java via SQLiteJDBC. It is very good embedded database. For Java, it might be easier to use Derby though.
You might also want to look at HSQL and H2, which are both open source embedded databases written in Java.
Firebird Embedded - just needs couple of DLL files and you have full database in your hands. Have been using it for years.
How to use it in Java
Look into SQLite. I haven't used it, but I've had apps that claimed to use it, and I couldn't tell the difference.
How about SQLite?
It has good performance, and with one user you don't have to worry about concurrency.
Oracle Berkeley DB: http://www.oracle.com/database/berkeley-db/index.html