Re: Problem with Entity Modeler and prototypes when switching DB

From: David Avendasora (webobject..vendasora.com)
Date: Mon Mar 10 2008 - 09:44:44 EDT

  • Next message: Alan Zebchuk (JIRA): "[OS-JIRA] Created: (WOL-750) Entity Modeler opening multiple connections to the DB"

    Whoops. Sorry if I wasn't clear, but I was commenting _only_ about the
    attribute name. Everything else, I agree on 100%!

    I was just trying to get across that if Mike does add the ability to
    reset the attribute values (please do!), that it _shouldn't_ reset the
    attribute name.

    Dave

    On Mar 10, 2008, at 9:29 AM, David LeBer wrote:

    >
    > On 10-Mar-08, at 9:15 AM, David Avendasora wrote:
    >
    >> On Mar 8, 2008, at 12:49 PM, Mike Schrag wrote:
    >>
    >>> Well, for instance, attribute name is defined in the prototype.
    >>> Should changing prototypes override your attribute name?
    >>
    >> Nooooo!!!! Please don't replicate all of EOModeler's "features"! :)
    >>
    >> EOModeler did do this, and it was the #1 reason I didn't go back
    >> and add prototypes to all my attributes after I had built the model
    >> originally without them, and it was the first thing I did after
    >> changing to Entity Modeler.
    >>
    >> And yes, I know that was a rhetorical question. I know you wouldn't
    >> do that.
    >
    > Yes, but as it's been pointed out, there are legitimate occasions
    > where overriding set values is the desired behaviour so having this
    > a an opt-in/out option would be useful.
    >
    > ;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
    > --
    > Toronto Area Cocoa / WebObjects developers group:
    > http://tacow.org
    >
    >
    >
    >

    This archive was generated by hypermail 2.0.0 : Mon Mar 10 2008 - 09:46:17 EDT