Re: Complex EOQualifier format
Re: Complex EOQualifier format
- Subject: Re: Complex EOQualifier format
- From: Steven Mark McCraw <email@hidden>
- Date: Wed, 4 Jul 2007 17:28:14 -0400
On Jul 4, 2007, at 5:15 PM, Pierre Bernard wrote:
I feel the urge to voice opinions about this.
- EOF is an ORM not a SQL generator. Its task is to allow you to
work in a pure OO work and make object graph management and
persistent transparent. Meaning: you want to do your processing in
Java, not in the database.
I can appreciate this, but there are times when you absolutely cannot
do your processing in Java. The example I posted earlier (which
fetches geographical points within a certain distance of other
geographical points) is a perfect example. You can do this in the
database and have a response to your users within seconds, or you can
do it in java and have a response to your users in minutes. It would
appear that the option you are left with here is fetching raw rows.
- You are free to extend EOF's magic by writing custom qualifiers.
I have some on my web site: http://www.bernard-web.com/pierre
That sounds like a neat idea, but I don't really know how you would
go about it. I downloaded your code just now and will have a look
when I have more time.
- qualifierWithFormat() is evil. 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
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden