• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: To Many Relationship to String
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: To Many Relationship to String


  • Subject: Re: To Many Relationship to String
  • From: Ken Anderson <email@hidden>
  • Date: Thu, 12 Aug 2010 14:43:41 -0400

Follow the golden software development rule:

1.  Make it work
2.  Make it work right
3.  If something is slow, figure out how to make it faster AFTER it already works right

Ken

On Aug 12, 2010, at 2:32 PM, Chuck Hill wrote:

> My vote: listen to Dave.  Quick and Dirty usually ends up Slow and Expensive and Dirty.
>
> Chuck
>
>
> On Aug 12, 2010, at 11:27 AM, Steve Peery wrote:
>
>> 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@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> --
> Chuck Hill             Senior Consultant / VP Development
>
> Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
> http://www.global-village.net/products/practical_webobjects
>
>
>
>
>
>
>
> _______________________________________________
> 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

 _______________________________________________
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

  • Follow-Ups:
    • Re: To Many Relationship to String
      • From: Mark Ritchie <email@hidden>
References: 
 >To Many Relationship to String (From: Steve Peery <email@hidden>)
 >Re: To Many Relationship to String (From: David LeBer <email@hidden>)
 >Re: To Many Relationship to String (From: Steve Peery <email@hidden>)
 >Re: To Many Relationship to String (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: To Many Relationship to String
  • Next by Date: problem with AjaxDatePicker solved...
  • Previous by thread: Re: To Many Relationship to String
  • Next by thread: Re: To Many Relationship to String
  • Index(es):
    • Date
    • Thread