I see! I'd wondered why those constants were getting tossed in
there. That's very fancy! Thanks guys!
Mark
On Jul 4, 2007, at 5:44 PM, Ken Anderson wrote:
Are you using EOGenerator? It creates constants for you for all
the names of your attributes. So, you would construct one like this:
EOKeyValueQualifier qualifier = new EOKeyValueQualifier
(User.LastNameKey, EOQualifier.QualifierOperatorEqual, "McCraw");
If you modify your model, EOGenerator will update the constants,
and your code will no longer compile. If you're using Eclipse and
WOLips, this pretty much happens automatically and then you can
just refactor.
Ken
On Jul 4, 2007, at 5:37 PM, Steven Mark McCraw wrote:
In a previous post, it was mentioned that
The qualifier string cannot be validated by the compiler. You are
tempted to write out attribute names in String, thus making
future evolutions of the model difficult. It is almost like
writing SQL
It looks like EOKeyValueQualifier still takes the attribute name
as a string in its constructor. How would the compiler validate
your (possibly changed) attribute names even if you weren't using
qualifierWithQualifierFormat?
On Jul 4, 2007, at 5:31 PM, Ken Anderson wrote:
You create them using instances of EOKeyValueQualifier,
EOAndQualifier, EOOrQualifier, etc. All
qualifierWithQualifierFormat does is build this structure for
you... sometimes poorly.
On Jul 4, 2007, at 5:28 PM, Steven Mark McCraw wrote:
How do you create your qualifiers if not with
qualifierWithQualifierFormat?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
