I had two questions about table design and format. I'm designing an application that has two tables. The first table will have -Many selects that return about 20 results on average. -Few inserts -Very few UPDATEs For this table it is not important that the newest inserts show up in selects immediately. So i was thinking of doing selects with insert delays and maybe a table lock for the update Now i understand that MySql does not support row locking, so i was wondering whether to use versioning with a MyIsam table or just use table locks. I'm looking to maximize speed and concurrency. Question1: Please give me a suggestion on the best way to approach this. The second table will have for every request sent by the browser: -Two selects that return data from a unique key ( select...where =unique key#) -one update that also update a unique key# Note that this will happen an a request scope and there maybe the occassional delete but that very insignificant. The site quotes "Concurrent users is not a problem if one doesn't mix updates and selects that needs to examine many rows in the same table. " Now is this true for the default table in MySql (which i believe is MyIsam) or do i need a special table structure. Note timing is important in this table so i cannot do low priority updates because the update has to happen with the selects in the request scope. Also the requests that come in are not necessarily unique ( they would be in most cases but not all) so they could be accessing the same row of the table. Question2: Would table locking be my best bet or will it be optimized with the default table. Please give me a suggestion on the best way to approach this. Thanks Ray --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
