Not that this helps, but all proper OS X (Cocoa-based) applications
store their preferences in the defaults database, so yes, that is a
tried and proven idea. It just seems like HSQLDB (or something) is
getting a bit confused from time-to-time. I like the XML idea Andrus
mentioned, since it is human readable and editable. And XML is very
enterprisey. :-)
/dev/mrg
-----Original Message-----
From: Tomi NA [mailto:hefes..mail.com]
Sent: Monday, May 01, 2006 5:51 AM
To: cayenne-use..ncubator.apache.org
Subject: Re: reverse engineering a postgresql database: no relationships
detected?
On 4/30/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
>
> On Apr 30, 2006, at 3:39 PM, Andrus Adamchik wrote:
>
> >> Of the top of my head, I can suggest xstream as an (as far as I've
> >> used it) a great serialization engine.
> >
> > Good idea. Serializing preferences to XML may be a better solution.
> > Embedded HSQLDB proved to be too unreliable. And I guess we can use
> > XSLT transforms to version the preferences.
>
> Using Cayenne for preferences is great for a few reasons (1) you can
> do real queries and (2) updates are incremental. I guess if we go
> XML, we'll have to manually partition the preferences into smaller
> manageable chunks and use XPath. Oh well...
Not that I'm against trying new things, but do you know of any other
application storing it's preferences in a database? It seems like a
major overkill to me...but then, I don't know much about the specifics
of the modeler code so take my comments with a grain of salt.
t.n.a.
This archive was generated by hypermail 2.0.0 : Mon May 01 2006 - 09:14:17 EDT