Re: ADC Core Data article

FROM : Jake Macmullin
DATE : Wed Apr 06 02:31:09 2005

In some senses I'm not surprised by Core Data's requirement that 
persisted classes inherit from a common parent - that's how WebObjects 
works.

However, other O/R frameworks allow you to persist 'plain old' objects. 
For example, Hibernate allows you to persist 'plain old Java objects' - 
so I'm not sure it is asking too much for an O/R framework which 
doesn't require that all persisted classes inherit from a common parent 
(other than object). Although perhaps some of Core Data's features such 
as the handling of 'undo and redo' would make this idea more difficult.

Regards,

Jake MacMullin

CSIRO Land and Water
GPO Box 1666 Canberra 2601
Ph 02 6246 5822
Fax 02 6246 5800
http://www.clw.csiro.au/staff/MacMullinJ/


On 6 Apr 2005, at 9:14 AM, Scott Stevenson wrote:

>
> On Apr 5, 2005, at 2:49 PM, Philip Mötteli wrote:
>

>>> Each entity definition in a managed object model requires the name 
>>> of the entity and the name of the class used at runtime to represent 
>>> that entity. By default, the class used is NSManagedObject, but the 
>>> class may be either NSManagedObject or a subclass thereof.

>>
>> I read that phrase 5 times. Is that really true? Only subclasses of 
>> NSManagedObject get managed persistency from Core Data?

>
> Trying to implement transparent persistence without a persistent 
> subclass is.... challenging.
>
>
>    - Scott
>
> --
> http://treehouseideas.com/
> http://theocacao.com/ [blog]
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list      (<email_removed>)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/
> jake.<email_removed>
>
> This email sent to jake.<email_removed>
>