Re: EOModler Questions..
Re: EOModler Questions..
- Subject: Re: EOModler Questions..
- From: Ray Ackland <email@hidden>
- Date: Wed, 7 Jan 2004 17:39:17 +1300
James,
Here is my thought process:
1) Each fetch from the database takes the database server a bit of time.
2) Receiving the rows from the database server, and converting them
into Enterprise Objects also take a finite amount of time.
3) The greater the number of attributes a table has, the longer to do
each of these steps.
4) The more related tables you have, the more fetches and hence more
time taken when you want to traverse the tables.
Hence, if there is a logical organisation of the table where attributes
naturally fit into their own little sub-group, then it could be worth
breaking the table into parts - each looking after the different group
and sharing a common id field (note: there are features in EOModeler to
accommodate this). This way, certain attributes which are not used for
anything at all in a particular web based application will never need
to be retrieved and things should be faster.
Having said all this, I wonder about the wording of your question.
Fetch Spec's are used to get a subset of the records, rather that a
subset of the attributes (unless you are doing custom fetches). I don't
see how you would use them in this case.
Regards,
Ray.
On 7/01/2004, at 17:02, james cicenia wrote:
I have been studying EOModeler and have been very diligent
in modeling my database. Now I am working with "Fetch Spec"
and again wondered...
If I have a large table and that table is used for reporting, editing,
printing and displaying, would it be better to create multiple entities
of the same table but with the smaller subsets of data that are needed.
For instance, I will be showing small lists on my web page in a panel
that will only need to show 4 attributes out of about 50... then I
will have
an interface to "expand" this listing to a full page with many
instances
but still only a subset of the 50 attributes, i.e, about 10.
So... is it better that I create all these entities with their
specific "Fetch Spec"
before I start development.... or just create the single table
entities and only
use the necessary methods to display the subset of attributes.
If this makes sense I would greatly appreciate any feedback here as I
am
just starting a new project with this tool and really would like to
start with
the proper foundation.
_______________________________________________
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.