Its weird, I dropped the indexes off that table, and re-added them but the queries used to take 5 sections but now take much much longer.
I did a little reading on the EXPLAIN command and it looks like my query without an index has 9427^15 rows to query. So thats where I am seeing the huge timeout come in. What are some general rules on indexing a table? I have a table like this: id, app_id, row_id, field_id, data int PRI KEY, int, int, int, blob when I query the table I am querying for an item in the data field, lets say I'm looking for 'widget' there are other records with the same row_id as widget so I also want to pull those out of the table too. I hope this makes some sense... Thanks, Matt On Fri, 2003-10-03 at 20:14, Jeremy Zawodny wrote: > On Fri, Oct 03, 2003 at 04:23:56PM -0400, Matt Babineau wrote: > > now the query isn't finishing executing and its killing my cpu... > > > > any idea how to rebuild the index on a table? > > > > or how to get out of this mess? > > Drop and re-add the index? > > Jeremy -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
