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

Re: EO-Modeler Again


  • Subject: Re: EO-Modeler Again
  • From: Colin Clark <email@hidden>
  • Date: Fri, 9 Jan 2004 17:34:04 -0500

Hi James,

In answer to your question, I guess it depends on how much business logic you need to have for this particular "portal view" on your website. If you're basically just displaying the raw data from the database, it seems more appropriate not to actually model this subset as a separate class in your data model.

It sounds like you may best be to simply fetch the desired Table1 records as raw rows, SELECTing only the columns you actually need for your special display. Generally speaking, it will offer effective performance and not introduce a potentially problematic design into your object model. When your application does need to access a particular instance of the full object and its associated business logic, you can fetch it when required.

Best of luck,

Colin


On Friday, January 9, 2004, at 12:50 PM, james cicenia wrote:

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.


---
Colin Clark
Dynamic Web/Database Developer
Resource Centre for Academic Technology,
University of Toronto
(416) 946-7592 / email@hidden
_______________________________________________
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.

References: 
 >EO-Modeler Again (From: james cicenia <email@hidden>)

  • Prev by Date: Re: direct to web query help for n00b
  • Next by Date: Re: direct to web query help for n00b
  • Previous by thread: EO-Modeler Again
  • Next by thread: Re: EO-Modeler Again
  • Index(es):
    • Date
    • Thread