On 30.11.2008, at 22:19, Ted Archibald wrote:
This app will have a small user base (<6), and will be in a
controlled environment. That said I don't intend on switching
objects that often, but approximately one in every 1000 objects
created would have to be changed due to data entry errors.
Ultimately the object type should be set for life, save for the
occasional error.
It seems to me that it'd be easier to handle the errors generated
when fetching/saving, rather than create and maintain a helper class.
I've played that part once years ago and I will never do it again. Why
make your life harder than it should be? Write method that creates a
new objects, copies the attributes, and re-attach all relationships,
get rid of the old object and be done with it. Nice, clean, working.
Changing one under the nose of EOF - you have been warned!
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
