Question - table size
Question - table size
- Subject: Question - table size
- From: Kent Harris <email@hidden>
- Date: Fri, 27 Feb 2004 09:50:06 -0800
I've got a table that is currently split into two tables because each
part is accessed at different times and for different reasons -- I was
thinking performance, why access the whole table when I only need one
part at any given time? Its a one-to-one relation between the tables
with propagate primary key. One of the tables is hit during batch
processing once a day whilst the other is hit occasionally during
web-driven activity.
However, it makes the user interface (maintenance by an operator)
crummy via a direct-to-java-client app. with a dynamic/rule-based
generation of the GUI. If I combine the two tables into one to improve
the user interface will the faulting mechanism help me out or will an
entire record always be read from the underlying database (mySQL)?
Does it really matter since the difference in record size is, oh say
1000 bytes combined or 500 bytes each when separated.
Guidance by the experienced is always greatly appreciated.
- Kent
_______________________________________________
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.