Re: "extends EOGenericRecord" or "extends EOCustomObject"?
Re: "extends EOGenericRecord" or "extends EOCustomObject"?
- Subject: Re: "extends EOGenericRecord" or "extends EOCustomObject"?
- From: Ricardo Strausz <email@hidden>
- Date: Thu, 15 Jan 2004 17:55:37 -0600
IMHO, the main difference is that, when you implement a customObject,
you have the ``variables'' (atributes) at hand so, to access them, you
do not nead to use the accessor methods; this is quite usefull if you
are doing sofisticated logic. The main disadventage is that you have to
take care of some of the ``magic'' provided by a genericRecord (like
notify changes, so they can be spreaded).
I had not notice any adventage in performence (memory, time) while
using customO instead of genericR.
Dino
On Jan 14, 2004, at 6:06, Kieran Kelleher wrote:
Is there anyone out there who is extending EOCustomObject for their
java entity classes rather than extending EOGenericRecord?
What are the primary benefits to using EOCustomObject over
EOGenericRecord subclasses for EO's?
Besides the extra hand-coding and higher maintenance of
EOCustomObject, is there performance disadvantages (for example memory
usage?)
Any advice is appreciated.
Thanks, K
____________________________________
OS X 10.3.2 / WO 5.2.2 / MySQL 4.0.16
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.