• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Complex EOQualifier format
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Complex EOQualifier format


  • Subject: Re: Complex EOQualifier format
  • From: Pierre Bernard <email@hidden>
  • Date: Thu, 5 Jul 2007 03:08:03 +0200

One really neat solution for doing such things is having a stored procedure which fills in a temporary table. Can't remember the Oracle name of those. They are private to a session and disappear when the session is closed.

The stored procedure computes a unique ID and returns it. That same ID is assigned to all the rows that make up the operation's result. You then do a simple fetch with (uniqueID = myID) to get your result as array of read only EOs.

Pierre


On Jul 4, 2007, at 11:28 PM, Steven Mark McCraw wrote:


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:
email@hidden


This email sent to email@hidden

- - - Houdah Software s. à r. l. http://www.houdah.com

HoudahGeo: One-stop photo geocoding
HoudahSpot: Powerful Spotlight frontend



_______________________________________________
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


References: 
 >Complex EOQualifier format (From: Steven Mark McCraw <email@hidden>)
 >Re: Complex EOQualifier format (From: Steven Mark McCraw <email@hidden>)
 >Re: Complex EOQualifier format (From: Mike Schrag <email@hidden>)
 >Re: Complex EOQualifier format (From: Steven Mark McCraw <email@hidden>)
 >Re: Complex EOQualifier format (From: Pierre Bernard <email@hidden>)
 >Re: Complex EOQualifier format (From: Steven Mark McCraw <email@hidden>)

  • Prev by Date: Re: Help installing WebObjects on a PC still required
  • Next by Date: Re: WOBuilder Replacement
  • Previous by thread: Re: Complex EOQualifier format
  • Next by thread: Re: Complex EOQualifier format
  • Index(es):
    • Date
    • Thread