I suppose I'll clarify a bit 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. On Sun, Nov 30, 2008 at 8:52 PM, Mike Schrag <[EMAIL PROTECTED]> wrote: > My personal advice... Don't do it. >> > 2nd that .. It's almost always a red flag of an incorrect design. Objects > rarely change types, but they often change roles. It sounds to me like > maybe your model isn't quite right here and those objects should have > another relationship that is changing rather than the intrinsic property of > the object. > > ms > > _______________________________________________ > 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/ted.archibald%40gmail.com > > This email sent to [EMAIL PROTECTED] >
_______________________________________________ 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]
