Re: EOModeler Again...
Re: EOModeler Again...
- Subject: Re: EOModeler Again...
- From: Ricardo Strausz <email@hidden>
- Date: Fri, 9 Jan 2004 12:29:06 -0600
Hola James!
As Chuck metioned, 200 atribute for an object is too much...
I have had a simmilar problem while modeling "product descriptions" in
an enterprise (evethough I use Cocoa/EO, the problem is almost the
same).
Most of the atributes I was using was numbers (which translates in
selected buttons in an array of switch buttons) and some other data
type (more user friendly, like a string with a user-readable
descriptions).
My solution was to split the data in a more handly number of entities
and put them in a one-to-one relation. The main entity ONLY contains
the most used atributes (some 10 atributes) and only when the user
neads to see more detail, via the mentioned relation, the other
atributes (in the other entities) where retrived from the db and
manipulated to translate them into the GUI.
The resulting code is then partitioned in more workable pices... and
the time response is too much better.
Suerte!
Dino
On Jan 7, 2004, at 23:13, Chuck Hill wrote:
Finally, 200 columns? Wow. Wow. That is a lot for one table. With
accessors/mutators that gives a minimum of 400 methods for the Project
class and you've not even started to add functionality. Personally,
I'd
take a long, hard, close look at this and see how some of this can be
broken out into other tables. I'd think this would be worth it just
for
abstraction and organization's sake.
_______________________________________________
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.