Re: EOModeler and more
Re: EOModeler and more
- Subject: Re: EOModeler and more
- From: Arturo Pérez <email@hidden>
- Date: Sun, 11 Jan 2004 21:47:46 -0500
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.
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.
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.
----
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.