Re: EOModler Questions..
Re: EOModler Questions..
- Subject: Re: EOModler Questions..
- From: Drew Thoeni <email@hidden>
- Date: Wed, 7 Jan 2004 20:09:04 -0500
Like Ray, I am not sure I am clear on your use of the word attribute.
It may help if you share the data structure of this table. It is
possible some of these attributes should be in other tables (50, while
possible, is a large number of columns for a normalized data model).
Assuming, though, you mean columns, and being more of a purist in terms
of database design, I'd recommend keeping one table for these reasons:
1) If you're going to expand out the attributes to show more, you're
going to have to fetch those. The fewer fetches the better. I'd
recommend fetching them all in the first place and caching them for the
(presumably) short duration of the web transaction. The fecth spec
you're building in EOModeler generates SQL like SELECT ATTRIBUTE_A,
ATTRIBUTE_B FROM TABLE_2 WHERE ATTRIBUTE_N = "ABC"; (or some such). The
default for EOModler is to return all attributes (columns).
2) Good database design would have all records of the same type in the
same table, which leads (in WO) to a EO Class. Splitting this data into
separate tables will only cause problems later if you need to get at
all the records (to sum, count, list, etc.).
On Jan 6, 2004, at 11:02 PM, james cicenia wrote:
Hello -
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.
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.
_______________________________________________
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.