Re: Embedded database engine in Cocoa?
Re: Embedded database engine in Cocoa?
- Subject: Re: Embedded database engine in Cocoa?
- From: Chris Hanson <email@hidden>
- Date: Tue, 22 Jan 2002 21:40:36 -0600
At 2:20 PM -0800 1/22/02, Svensson, Conny wrote:
I'm looking for a small and effective relational database engine to include
in my freeware Cocoa app. It doesn't need to handle multiple users. I'm not
looking for a server-client database solution ala Oracle. Just a small
engine to be included in my app transparent from the user. I have looked
around and searched the boards but haven't found anything that fits. Since
my application is freeware I don't want to pay a fee to license it. I want
to focus on the application's functionality not on writing my own database
engine which I guess some of you would suggest. Has anybody written anything
you would like to share? Or do you have any experience with anything like
this that you could point me to? Or do I need to write this myself...
If it were part of Cocoa and the runtime were distributed with Mac OS
X, the Enterprise Objects Framework with the Flat-File Adaptor would
fit this bill perfectly.
Could I beg you to file a bug -- excuse me, "enhancement request" --
at <
http://bugreport.apple.com/> with your exact text above? Please?
The more people that do so, the more likely it is that Apple will
realize databases are Important. (Every bug filed gets reviewed and
classified and re-reviewed etc. at Apple, which is why I'm asking you
go this route. And Apple people have said it's a good route to get
our concerns heard.)
Thanks so much. Sorry I don't have any suggestions as to products
you can embed.
One idea I had for something I'm working on is to implement a
simplified EOF that keeps track of the attributes and relationships
in your model objects. Your model objects would all be instances of
xxxGenericRecord subclasses, which would in turn refer to xxxEntity
objects for this metadata.
It would also handle serializing your model objects to arrays of
dictionaries by replacing relationships with foreign keys, and
deserializing them from arrays of dictionaries by pulling in all the
simple attributes and then sending the objects
-awakeFromPropertyList:(NSDictionary *)plist. The serialized form
could easily be converted to and from XML files on disk by
NSDictionary.
This shouldn't take too long a time to design and implement, but
unfortunately I've got other, funded projects on my plate at the
moment. If I were able to take this on, I'd do it as Open Source
(BSD-licensed) so there would be a real and easy answer for questions
like yours in the future. ;)
-- Chris
--
Chris Hanson | Email: email@hidden
bDistributed.com, Inc. | Phone: +1-847-372-3955
Making Business Distributed | Fax: +1-847-589-3738
http://bdistributed.com/ | Personal Email: email@hidden