• 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: EOPrototype in Entity Modeler question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOPrototype in Entity Modeler question


  • Subject: Re: EOPrototype in Entity Modeler question
  • From: "Ricardo J. Parada" <email@hidden>
  • Date: Thu, 29 Oct 2009 17:59:01 -0400


On Oct 29, 2009, at 5:39 PM, Mike Schrag wrote:

oh wait ... you're going from no prototype to a prototype. yeah i'm not sure it will remove those -- as far as it knows you have an override of those values. this has been a debate i've had with myself for a while (and i think with the list a couple years ago, too), whether if you set a prototype, should it automatically replace every prototyped value in the attribute. the reason i have avoided this is that i tend to not implement features that LOSE information. however, it's debatable in this case what your intent actually IS -- if you set a prototype, PROBABLY you mean you want all the settings of the prototype applied. This gets a lot hazier, though, if you're talking about the width of a string -- if you change from one string prototype to another, did you intend to blow away the width? maybe only on the ones that explicitly set a width, i guess?

That makes total sense. :-)

In my original email I was looking for a way to clear all the values so that there are no overrides and then set the prototype. So that's really a feature request. But I'm handling it manually right now. :-) I can live with that. I use subclipse's Team Synchronize view to see these things and clean them up.

anyway, i'm not SURE that's what you're seeing but I suspect it is. is valueClassName being removed at least? i don't test much going from no prototype to a prototype, so i'm sure there are weird edge cases of this.


Yes, valueClassName is being removed!

By the way, how does the Data Type chosen for an attribute affect me? For example, I see different options related to dates / times: i.e. Date, Date (MSSQL), Time, Timestamp. For new attributes I just leave that with the default once I pick the prototype (either date or dateTime). But for existing attributes where I have the Data Type already selected and then choose a prototype I'm not sure how changing Data Type would affect me.

For example, if my existing attribute named "creationDateTime" had a Data Type of Timestamp selected and no prototype. And then I set the prototype to dateTime and change the Data Type to Date. Will that affect me somehow? :-)



Thanks,
Ricardo

_______________________________________________
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


References: 
 >EOPrototype in Entity Modeler question (From: "Ricardo J. Parada" <email@hidden>)
 >Re: EOPrototype in Entity Modeler question (From: Mike Schrag <email@hidden>)
 >Re: EOPrototype in Entity Modeler question (From: "Ricardo J. Parada" <email@hidden>)
 >Re: EOPrototype in Entity Modeler question (From: Mike Schrag <email@hidden>)
 >Re: EOPrototype in Entity Modeler question (From: "Ricardo J. Parada" <email@hidden>)
 >Re: EOPrototype in Entity Modeler question (From: email@hidden)
 >Re: EOPrototype in Entity Modeler question (From: "Ricardo J. Parada" <email@hidden>)
 >Re: EOPrototype in Entity Modeler question (From: Mike Schrag <email@hidden>)

  • Prev by Date: NPE from woapplication task at Ant build time
  • Next by Date: EOAttribute's Data Type question
  • Previous by thread: Re: EOPrototype in Entity Modeler question
  • Next by thread: Sharing a Model using Eclipse
  • Index(es):
    • Date
    • Thread