[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> on Thursday, October 07, 2004 1:34 PM said:
> Can you see where the column "possible_keys" is NULL for every table? > That means that there are NO (none, zilch, nada, zero) indexes that > can be used to save your database engine from the trouble of doing a > full table scan for EACH AND EVERY MATCH in your query. I don't even > see where you defined any PRIMARY KEYS on any of your tables. that's weird because i've definitely defined PRIMARY KEYS. like i know i had a PK on products.id... but admittedly i don't really know too much about indexes or keys (primary, or foreign). > (May I > suggest you hit web and do a little homework on indexes and primary > keys?) you certainly may. :) might you have any specific links for me to look at? > > Try adding these indexes then let me know how your query performs: i performed your suggested operations and the query runs at the same speed. it nows reports at 2.22. i did read in the link you gave me in the your first post about the ANALYZE table; query so i'll try doing that right now and then see how if it changes. after doing the ANALYZE TABLE table; query on a few tables the time is now down to 2.07. (i think i made a mistake in my original time of 2.03... maybe it was 2.23. i know for sure it was 2 seconds and *something*.) thanks, chris. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
