On Feb 21, 2009, at 04:30, Paul Hoadley wrote:
I see a thread from 2003 [1] that seems to indicate that uniqueness
of an attribute isn't expressible in an EO model. I take it the
only way to add such a constraint, then, is manually?
AFAIK: yes.
However, it *might* be possible to enhance EntityModeler to include
this info in the EOModel, and thereby to generate SQL that does this
for you... It would not be information present at runtime, in the
programatic rep of the model, which could be a source of confusion,
but it might be a convenient feature nevertheless. And who knows,
maybe Apple would pick up on it and include this info in the EOModel
standard... Any thoughts on this from WOProject folks?
F
_______________________________________________
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]
