Are there any alternative to SQLite to use as embedded database engine?
+2
A:
Sure. This page shows a couple non-SQLite frameworks (besides Core Data):
I have no idea how awesome these projects are, so YMMV.
If you're looking to avoid external dependencies (ie, not shipping a framework with your app), then you're stuck with SQLite or CoreData. CoreData can use XML as its format, but it has some disadvantages. SQLite is definitely the most recommended CoreData backend.
Dave DeLong
2010-07-03 23:08:26
why the downvote?
Dave DeLong
2010-07-03 23:19:29
I wasn't the one who downvoted it, but I don't think any of your suggestions are *embedded* database engines.
JWWalker
2010-07-04 00:44:34
@JWWalker if you define "embedded" as "shippable with the application", they are, since they're for frameworks (and the question is tagged `osx`)
Dave DeLong
2010-07-04 01:08:59
I meant to ask about an embedded database engine without external dependencies, but I didn't made that explicit. I don't see anything wrong in the interpretation given by Dave DeLong. About the links he gave, all the three frameworks are reported to be for Cocoa; even if I understand that ODBC was born for Windows, I expressly excluded that.
kiamlaluno
2010-07-04 02:53:21
@Dave DeLong: May you modify the text of your answer (it's enough you add a new line)? I made something wrong, and now Stack Overflow tells me that I voted 28 minutes ago, and my vote is locked. I think it must be I clicked twice, annulling the vote I made (in fact, I don't see the orange arrow).
kiamlaluno
2010-07-04 03:12:19
+1
A:
There are a couple of alternatives to SQLite if you want to have an embedded database engine, such as:
Be sure to also check the licensing terms.
EDIT:
Firebird is licenced under a derivative MPL licence, so it can be used in closed-source applications (see FAQ). The other two are dual-licenced so you need to pay if you are going to use them in commercial applications.
the_void
2010-07-04 10:35:33