On 8/31/06, Harrison Fisk [EMAIL PROTECTED] wrote:
Hello,
On Aug 31, 2006, at 5:12 AM, Kim Christensen wrote:
Hey list;
I posted this message under an earlier thread which touched the same
subject - but I realized my case could be slightly different, thus
posting a new thread here. Sorry
On 8/31/06, Harrison Fisk ** [EMAIL PROTECTED] *** wrote:
Hello,
On Aug 31, 2006, at 5:12 AM, Kim Christensen wrote:
Hey list;
I posted this message under an earlier thread which touched the same
subject - but I realized my case could be slightly different, thus
posting a new
Hey list;
I posted this message under an earlier thread which touched the same
subject - but I realized my case could be slightly different, thus
posting a new thread here. Sorry for any inconvenience.
I have two tables, one of which is a list over products which all have
unique product id's
: Kim Christensen [EMAIL PROTECTED]
To: MySQL List mysql@lists.mysql.com
Sent: Thursday, August 31, 2006 5:12 AM
Subject: Insane execution time for JOIN query
Hey list;
I posted this message under an earlier thread which touched the same
subject - but I realized my case could be slightly different
from default.
- Original Message -
From: Kim Christensen [EMAIL PROTECTED]
To: MySQL List mysql@lists.mysql.com
Sent: Thursday, August 31, 2006 5:12 AM
Subject: Insane execution time for JOIN query
Hey list;
I posted this message under an earlier thread which touched the same
subject
VARIABLES LIKE %buffer_size
- Original Message -
From: Kim Christensen [EMAIL PROTECTED]
To: MySQL List mysql@lists.mysql.com
Sent: Thursday, August 31, 2006 9:12 AM
Subject: Re: Insane execution time for JOIN query
On 8/31/06, Brent Baisley [EMAIL PROTECTED] wrote:
How about posting
On 8/31/06, Brent Baisley [EMAIL PROTECTED] wrote:
hmmm, not sure why it's only scanning 89K records from the products table, I
would think it would scan the whole table. It is
scanning the entire items table, which I would think it wouldn't do.
Well, the query in question actually did do
Kim,
The first thing I'd do is run a MyISAMChk on the table to see if the index
is damaged. The second thing I'd do is run Optimize on the tables regularly
because after a lot of rows have been deleted it leaves holes in the table
which slows down table performance.
Of course you
Hello,
On Aug 31, 2006, at 5:12 AM, Kim Christensen wrote:
Hey list;
I posted this message under an earlier thread which touched the same
subject - but I realized my case could be slightly different, thus
posting a new thread here. Sorry for any inconvenience.
I have two tables, one of which
