Re: A CoreData Limitation?
Re: A CoreData Limitation?
- Subject: Re: A CoreData Limitation?
- From: Raffael Cavallaro <email@hidden>
- Date: Wed, 18 May 2005 18:02:25 -0400
On May 18, 2005, at 4:31 PM, Shawn Erickson wrote:
One way to think of it is that in your schema you should model not
only your application data but also how its structure could be
modified at runtime (just another piece of data to model). In other
words don't add a property to an entity (aka column to a table) in
your schema at runtime instead define your schema such that you can
capture that additional data and relate it as needed (could be a
simple as table that captures named or unnamed attributes that can
be related to other objects in the schema).
Of course how flexible your schema is needs to balanced against how
complex you want it and how likely schema changes are, etc. It
isn't an exact science.
This last bit (not being an exact science) is why greater flexibility
to change schema would be desirable. I was simply noting that as it
now stands, significant changes to ones data model are likely to
necessitate changing one's schema. This will of course not be doable
at runtime given Objective-C's current inability to unload classes.
FYI it is known that the Apple's Objective-C runtime is getting
closer to allowing for unloading of classes at runtime [2]. Also GC
is being worked on for Apple's Objective-C runtime [3].
These would both be very welcome additions imho.
P.S. I'm heeding Bill Bumgarner's warning about drifting off topic
and won't continue the forked thread - at least not in this forum ;^)
regards
Raffael Cavallaro, Ph.D.
email@hidden
_______________________________________________
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