Sqlite Alternatives For C++
Solution 1:
Stay with SQLite but find a good C++ library for this.
This StackOverflow question should help you ...
Solution 2:
I would argue that the added dependency on a wrapper library is not worth the cost of having to deal with the costs of that extra dependency. You don't want to be stuck debugging these wrapper libs when the documentation for them may be scant. SQLLite is bound to be more stable and have better documentation and therefore a more reliable dependency.
I would either deal with sqllite or wrap it yourself in some intelligent way based on your end application.
Solution 3:
It sounds as if a database is the only real option for you. If you chose SQLite or MySql or Postgres does not really matter in the column index point, though.
Maybe what you really want is a better database abstraction. You might want to try Poco, it has a great one: http://pocoproject.org/
Solution 4:
Berkeley DB aka SleepyCat. If you search the archives there is an article by Mike Olsen that talks about the major disadvantages of SQL in any project. There is another followup article within the last year that suggests that SQL is on it's way out because the ORM layers are getting so much better.
Solution 5:
If SQL syntax is not important to you, I recommend MetaKit - It is a slightly different approach but it quite powerful and I personally know of more than a few commercial projects which use it successfully, even on embedded systems.
This Tutorial is quite helpful to get started.
Post a Comment for "Sqlite Alternatives For C++"