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, 18 May 2005 09:21:35 +0200
On 5/11/05, Bruno Blondeau <email@hidden> wrote:
All these solutions are real nightmares... I thought CoreData was
supposed to help developers make things easiers.
What it makes easier is writing the data model, and getting prototype
UIs going. When the data model's easier to put together, it gives you
more time to leave room for expansion as well.
In any case, CoreData makes it easier to properly design and implement
a good model. For that you need to know how to design a good model,
and that involves doing things to make your model expandable. Read up
on database design, and you'll see that adding columns to an existing
table generally isn't the solution suggested, you just add an extra
table. In CoreData, if you need to store new data in your new version,
you create a new model. It can extend the old one, but the point is
that it's a _new_ model.
CoreData (for now) isn't designed to replace real databases.
It seems to be aimed at replacing most file formats (well, Apple
advises developers to consider using CoreData for all new
developments). Is a new model a practical solution for a document-based
application?
Let's imagine I have a document storing events:
"Table" EVENTS:
Title
Start Date
End Date
Now, if I want to add a Description to each event, what am I supposed
to do?
When using the XML data store, each description is blanked by default
and everything is fine. This is the expected behavior. This isn't the
case with the SQLite data store, and this looks like a bug to me...
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