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

Re: EOModeler and more


  • Subject: Re: EOModeler and more
  • From: james cicenia <email@hidden>
  • Date: Sun, 11 Jan 2004 21:02:31 -0600

On Jan 11, 2004, at 8:47 PM, Arturo Pirez wrote:


On Jan 11, 2004, at 9:26 PM, james cicenia wrote:

I am putting as many of my queries into the modeler via adding Fetch
Specifications.
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?


Details?


Yes.. the SQL shows "all" the attributes/columns of the class and not the
few I wish.

Right. Because, via EOModeler, you've told EOF that you're going to need
all the attributes. And you probably will, eventually. It seems that you
still haven't modeled your schema properly from the new perspective you're
attempting to achieve.


An assumption in EOF is that you're generally going to want all the attributes
of the classes you're defining. After all, if the attribute is superfluous
then why did you model it? There's no concept really of "sometimes I need these
and sometimes I need those." If that's what you need to do then you need two
classes with the differing attributes with a relationship between
them (again google "j2ee dependent object"). And that implies at least two
tables.

Not really. If I am showing a Portfolio screen which has a couple small lists of project_requests
wouldn't that best be modeled via the Raw Fetch into a dictionary? Than up clicking a project_request
I could instantiate the full project_request object.


Also, I did read the Vertical vs. Horizontal explanation and feel that I have my application now
modeled correctly.




I guess it is time start diving headlong into the Framework.

I fear for you :-) I've only twice needed a raw SQL statement in EOF.

Hmm, than how would you have modeled my above scenario? You would just instantiate
the complete list of project_requests? Sounds very expensive to me in terms of performance.



Once was to
pass an Oracle hint (evil things those hints) and the other was to indicate to Oracle
that a query didn't need all the data (i.e. to use rownum). Never did I need to delve
into the murkier areas of "the Framework."


You may want to reconsider.

That is why I am taking my time.

-James
_______________________________________________
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 and more
      • From: Arturo Pérez <email@hidden>
References: 
 >EOModeler and more (From: james cicenia <email@hidden>)
 >Re: EOModeler and more (From: Arturo Pérez <email@hidden>)

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