On Jul 21, 2006, at 4:48 PM, Stefan wrote:
I have written an app that uses the built-in database. What are
the pros and cons of using this for storage of prefs vs. a prefs
file?
If you migrate your account from one mac to another, the prefs get
moved orderly.
I don't believe this is true. The built in database (the Old
REALDatabase or REALSQLDatabase) are just flat file which should be
no different than a preference file. It would be a nightmare to move
prefs if they were stored in a MySQL or another similar database engine.
Personally, I don't think the format is important (flat-file DB, XML,
text or binary). But I do think that implementing and maintaining a
DB-prefs solution is more work than some of the other options.
The only other disadvantage that I can think of is that the DB
engines change quite a bit. For example the SQLite 2.0 format is not
compatible with SQLite 3.0, and that would require you to be able to
read both and have a conversion function. Since REALbasic started
with the 3.0 engine, this really has not been a problem, but it might
be a problem when 4.0 comes out (no I idea, just a thought). If
REALbasic 2007r3 comes out with an incompatible SQLite version, then
it might force you to do a lot of work to all apps which use your
your preference system.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
