Re: CoreData issue when updating a file format
Re: CoreData issue when updating a file format
- Subject: Re: CoreData issue when updating a file format
- From: Bruno Blondeau <email@hidden>
- Date: Wed, 11 May 2005 19:20:49 +0200
Non-trivial, yes. Tedious, yes. But migrating data models is
typically hard.
All these solutions are real nightmares... I thought CoreData was
supposed to help developers make things easiers.
Model changes are very frequent in typical applications and they should
be handled automatically in simple cases (if an attribute is added, add
the column, and use the default value for example). Well, this is what
is done in the XML case, so I really don't understand why it isn't the
case with the SQL data store...
How is Apple expecting developers to easily use CoreData if model
migration isn't handled... well, this maybe won't be a problem for v1
applications, but be prepared to hear a lot of complains from
developers new to CoreData, or even new to Cocoa, when they will have
to update the model of their applications...
Tiger really seems to be rushed... CoreData doesn't seem to be feature
complete... And let's not speak about the incomplete NSTreeController
class (many accessors missing with no workarounds, many convenience
methods missing, no drag&drop support...). I'm really disappointed.
(and it's not specific to Cocoa... just take a look at Quartz 2D
Extreme...)
Anyway, coming back to CoreData and model migration, any sample code
would be welcome. I have several application ideas that could rely on
CoreData, but I'm for now stopped unless an elegant and easy solution
is found :-( (well, XML may be the solution, but it's going to be way
too slow for at least one of my applications...)
Bruno
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden