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

Re: EOModeler Again...


  • Subject: Re: EOModeler Again...
  • From: james cicenia <email@hidden>
  • Date: Wed, 7 Jan 2004 15:33:45 -0600

Chuck -

Thank you very much for your reply. It seems others have a similar confusion.

please see my response....

James,

You seem to be confusing Entities and fetch specs with tables and views.

not really... though they are somewhat similar to me I admit.

While you can link multiple entities to the same table for performance
reasons I'd try to avoid it as it can lead to problems. If you find out
that you need to do something like this for performance reasons (and I'd
only do so after evidence that performance was a problem) then "raw row"
fetches are a more appropriate solution.


In your case I'd model two entities, Portfolio and Project. I'm not clear
on what you intend by "portal", perhaps that is another entity.

Portfolio to project is a one to many relationship. I will be using the following
patter a lot. I wish to display in a quadrant (portal) on my web page a "canned"
query result in this case of projects. The Project table/entity is very large with
about 200 attributes/columns. The quadrant will only wish to display the
top 10 projects (based upon the "canned" query) and only about 5 attributes/columns of the selection.


So I thought that I could make all those "canned" queries "prefetches" inside
of their respective EOM entity. This entity would not be "the" main Project entity but in fact an additional entity that models a subset of the Project table columns


Would this make sense?

.

You will have much more success with WO if you stop thinking about tables
and fields and just think about objects. Chances are there will be no
performance problems and you are worrying needlessly. You might also want
to reconsider the design of the project table. Is it fully normalized?

My tables are well normalized and all my relationship between tables accurate
and accounted for.
_______________________________________________
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 Again...
      • From: Chuck Hill <email@hidden>
References: 
 >Re: EOModeler Again... (From: Chuck Hill <email@hidden>)

  • Prev by Date: pbx scripting question
  • Next by Date: Re: JNDI/LDAP and multivalued attributs
  • Previous by thread: Re: EOModeler Again...
  • Next by thread: Re: EOModeler Again...
  • Index(es):
    • Date
    • Thread