EODataSource confusion :-(
EODataSource confusion :-(
- Subject: EODataSource confusion :-(
- From: Kieran Kelleher <email@hidden>
- Date: Wed, 2 Feb 2005 11:14:51 -0500
Apologies for my elementary confusion....
Could someone briefly explain/advise what is the advantage of using EODataSource objects instead of just an NSArray of objects? I did look at the EODataSource concepts in the API docs, but still not sure whether this is something "I should really be using to make WO development easier"? Am I better off creating and setting an EODataSource (setDataSource) when working with WODisplayGroups or simply using an NSArray and setObjectArray?
With respect to EODatabaseDataSource, a point of confusion for me is
deleteObject: removes the object from the data source (but does it literally delete the object permanently?)
insertObject: "The default implementation does nothing" ?! (So, what does it do?) Parameters: the object to insert into the current editing context (why would it not insert an object into the data source?)
Regards, Kieran _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden