Re: proper location for a database file
Re: proper location for a database file
- Subject: Re: proper location for a database file
- From: Glenn Howes <email@hidden>
- Date: Tue, 26 Nov 2002 23:11:55 -0600
On Tuesday, November 26, 2002, at 09:39 PM, Nicholas Riley wrote:
Of the applications you mentioned, iTunes exposes its music library
(~/Music/iTunes/iTunes 3 Music Library). So should iPhoto IMO, as
made clear by third-party programs such as 'iPhoto Library Manager'
which use hacks to get iPhoto to recognize multiple libraries.
What if you've got two Macs and want to copy or merge the library from
one to the other? By implementing documents as preference information
or imposing your own filing system, you're placing a rather arbitrary
restriction on people's working styles.
Well, if the database is done via the file system or in an opaque file,
the point is it's in a set location and the user can't choose different
ones. And, I don't mind merging databases; that's not very relevant to
document versus database; presumably a merge could be done with either.
I wouldn't call the design decision arbitrary, as I've decided
logically, I think, on a design which takes care of file handling for
the user because I'm under the impression it handles what 95% of users
require.
If it were a general purpose database program where people would want
to create different databases: one of their CDs and another one of
their collection of Ken dolls, then I would have to let the user deal
with file locations and launching the app as a separate operation from
loading a database. But there is only one kind of data, and the only
concern I have is whether there should be one database per user or one
per computer.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.