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

EO-Modeler Again


  • Subject: EO-Modeler Again
  • From: james cicenia <email@hidden>
  • Date: Fri, 9 Jan 2004 11:50:42 -0600

I have not been clear obviously.

I have modeled correctly all my tables and relationships completely
normalized in EO-Modeler.

The question is ... should I create new objects in EO-Modeler that
only have a subset of those attributes of the main class...

Table1 --> 50 columns
ClassTable1 -> 50 attributes

HOWEVER,

I need to show.. in many places of my application Table1
but showing only 5 columns. In other words, a small view
on the number of rows.

Should I create a new class with just those 5 attributes?
So that when I fetch those rows I only bring back the 5 attributes
vs. the 50? Then I could add those fetch specifications to that
class. Would this be better? More efficient? easier to code the
application on this foundation?


Sincerely,

James Cicenia - President/CEO
cell: 773.398.4649
www.jimijon.com
~~~~~~
The Internet's only Weekly Video Horoscope!
http://absinthium.jimijon.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: EO-Modeler Again
      • From: Arturo PĂ©rez <email@hidden>
    • Re: EO-Modeler Again
      • From: Chuck Hill <email@hidden>
    • Re: EO-Modeler Again
      • From: Colin Clark <email@hidden>
  • Prev by Date: Re: enable hot code replace possible?
  • Next by Date: Re: pbx scripting question
  • Previous by thread: test(please ignore)
  • Next by thread: Re: EO-Modeler Again
  • Index(es):
    • Date
    • Thread