ok, i've got this table (20 columns). keeping in mind how/which web pages would access them, i decided to keep the last 7 in a different table, since that data would only be shown if they clicked on a link they were interested in (30-40% probablity). although, when they do view it, i'd retrieve all columns from both tables.
Q 1. is this an advisable way to go about it? both tables created would have dynamic row length. when i started creating the first table, i realised that 7 out of the first 8 fields were fixed length. so i thought i'd furthur divide it into 2, first one with fixed length rows and the second being dynamic. so now i have 3 tables: t1 = 7 fixed len columns t2 = 6 dynamic t3 = 7 dynamic t1 and t2 will always be retrieved almost entirely and at the same time (i.e. one after the other). there's a 1-1 relation between t1, t2 and t3. and in 30-40% cases all of them. t1, t2 and t3. Q 2. any suggestions on the optimal may to go about this? i am aware of the disk seek time and data retrieval issues. Q 3. does mysql "not pay attention" to data that is (i) not mentioned in the SELECT fields list or (ii) WHERE clause? scanning time being considered different from return time. hence, putting t2 and t3 as one table. also, not using the mysql query cache. and would that change how the tables are designed? abs ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
