Re: EOAttribute's Data Type question
Re: EOAttribute's Data Type question
- Subject: Re: EOAttribute's Data Type question
- From: David Avendasora <email@hidden>
- Date: Fri, 30 Oct 2009 10:22:32 -0400
On Oct 29, 2009, at 9:50 PM, Chuck Hill wrote:
On Oct 29, 2009, at 6:42 PM, Mike Schrag wrote:
The only thing I ever touch are prototype, optionality, pk, and
locking. I don't change any other values.
That sounds like a sound policy to me. If you need to change
something else, make a new prototype!
Or if you have control over the DB consider changing the DB to match
the prototype. I've found lots of times where there is no prototype to
match the exact setting that are in the DB. At this point I as myself
which is better, to create a new prototype, or to change the settings
of the field in the DB to match an available prototype.
Instead of creating a varchar55 prototype, I often times will just
make the field increase the length in the db to 100, and then use the
varchar100 prototype. Obviously this does have impacts on the DB so
you need to take that into account. For me, being able to restrict
myself to the prototypes implemented by Wonder means less work in the
future (if I switch DB servers, I'd have to create new custom
prototypes that work with that DB where most of WOnder's prototypes
exist across all DBs.
Dave
_______________________________________________
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