Re: opposite method to objectMatchingKeyAndValue
Re: opposite method to objectMatchingKeyAndValue
- Subject: Re: opposite method to objectMatchingKeyAndValue
- From: Mike Schrag <email@hidden>
- Date: Sat, 21 Feb 2009 10:22:41 -0500
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?
5.4 added this, and Entity Modeler already supports it ... It depends
on your plugin as to whether or not SQL will be generated for it, and
I don't think migrations look at that (because the API isn't available
in 5.3).
ms
_______________________________________________
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