You are probably right. I too have paid for trying to "make it more efficient" many times in my coding career.
Steve On Aug 12, 2010, at 2:13 PM, David LeBer wrote: > > On 2010-08-12, at 2:05 PM, Steve Peery wrote: > >> I have an EO object that I want to have a to many relationship to a String >> object. I could create an EO object to hold the string and do a standard to >> many relationship but it seems wasteful. Is there a better way? >> >> Steve > > I will preface this with "I have no idea what your requirements are" but > speaking from experience: Anytime I've tried to cheap-out and take the quick > and dirty route with my model I've always regretted it. I would just bite the > bullet and model the relationship to an eo. I can think of a bunch of > downsides of working with a relationship modeled as an array or similar, and > not many upsides. And given the tools (EOGeneration, Migrations, etc) it's > not really a big deal to do it right. > > ;david > > -- > David LeBer > Codeferous Software > 'co-def-er-ous' adj. Literally 'code-bearing' > site: http://codeferous.com > blog: http://davidleber.net > profile: http://www.linkedin.com/in/davidleber > twitter: http://twitter.com/rebeld > -- > Toronto Area Cocoa / WebObjects developers group: > http://tacow.org > > > > _______________________________________________ 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]
