• 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: EOModeler
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOModeler


  • Subject: Re: EOModeler
  • From: Arturo PĂ©rez <email@hidden>
  • Date: Sun, 11 Jan 2004 21:39:45 -0500

On Jan 11, 2004, at 6:23 PM, james cicenia wrote:

My question now is an EOModeler question.

I am putting as many of my queries into the modeler via adding Fetch Specifications.

From a certain (useful in this case) perspective fetch specifications are not queries.


Queries in general can get you all kinds of data. Depending on the expertise of the
query writer the data can be amazingly useful or just outright garbage.


Fetch specifications are intended to retrieve objects matching certain criteria. So,
from that point of view they aren't generalized queries.


For example you can use a fetch spec to retrieve "Projects with user Joe as project
lead" but you can't really say "Count of projects with joe as project lead." (Of course,
there are various tricks but for our case here they would be counterproductive.) A
"count" isn't really any sort of EO class.


When I use "Raw Fetch" defining the attributes I want and then click the "SQL" tab
the SQL does not match my expectations. Is it supposed to?

There may be two things going on. First you should be using the query builder. In that
case you wouldn't be entering any SQL at all. If you try to EOModeler will overwrite your
lovingly handcrafted SQL. Second, if you using the Raw SQL capability then you're expected
to write the SQL the way that EOF wants it to be. I wouldn't recommend that you should be
doing any raw SQL at your level of knowledge of EOF. It will just encourage you to follow
a poor path to enlightenment :-)



Also, Is it possible to model a GROUP BY fetch specification in EOModeler.

EOModeler is not an ER tool although it can fake it sometimes. The fact that you're
asking this question indicates that you're still not seeing the objects you're trying
to model. What collection of your objects would benefit by being grouped?



----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: EOModeler
      • From: james cicenia <email@hidden>
References: 
 >EOModeler (From: james cicenia <email@hidden>)

  • Prev by Date: EOModeler and more
  • Next by Date: Re: EOModeler and more
  • Previous by thread: Re: EOModeler
  • Next by thread: Re: EOModeler
  • Index(es):
    • Date
    • Thread