Re: ADC Core Data article

FROM : John Brownlow
DATE : Fri Apr 08 17:47:50 2005

sounds like a job for Accessorizer

as usual the problem with cooking up accessors is exactly how to
implement them. We all tend to have different ideas of what accessors
should look like.

One side effect of the fact that, as the article states, managed
objects must inherit from NSManagedObject is that indexed structures
such as NSArray and so on are unlikely to be subclasses of
NSManagedObject and, more to the point, unlikely to be trivial to
manage.

Let's say you have an NSArray of NSManagedObjects. How do you persist
them while maintaining their indexed order? In the absence of an
NSManagedArray class which I have heard nothing about, it seems likely
that you will have to write your own 'managed array' class to do the
work for you.

Of course you could use NSCoding, but then you are doing something very
strange, which is coding a separately persisted object... so you now
have two copies in the persisted file!

Anyway, enough speculation. It will be interesting to see how these
issues are addressed.

On Apr 8, 2005, at 11:32 AM, Ralph Scheuer wrote:

>> If the former I am sure one could code up a tool that can read the
>> schema and do just that (generate a NSManagedObject subclass for ya
>> bristling with the accessors that you want). If you want Apple to do
>> that file an enhancement request against the tools.

>
> that's a brilliant definition of EOModeler, isn't it ;-)

--
John Brownlow
Deep Fried Films, Inc

http://www.johnbrownlow.com
http://www.pinkheadedbug.com