Re: Query takes terribly long

2004-09-20 Thread Bill Easton
9, so you won't ever see the values for 2004-02-29. Maybe you only care about an approximate result, and none of this matters. - Original Message - From: Dirk Schippers To: Bill Easton Cc: [EMAIL PROTECTED] Sent: Monday, September 20, 2004 6:06 PM Subject: Re: Query takes

Re: Query takes terribly long

2004-09-20 Thread Dirk Schippers
Y(putdatetime) <> 29) ORDER BY putdatetime DESC LIMIT 0,30 HTH, Bill == Dirk Schippers wrote: == Date: Sun, 19 Sep 2004 18:35:24 +0200 From: Dirk Schippers <[EMAIL PROTECTED]> To: Jocelyn Fournier <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: Query takes terribl

Re: Query takes terribly long

2004-09-20 Thread Dirk Schippers
=1 AND (MONTH(putdatetime) <> 2 OR DAY(putdatetime) <> 29) ORDER BY putdatetime DESC LIMIT 0,30 HTH, Bill == Dirk Schippers wrote: == Date: Sun, 19 Sep 2004 18:35:24 +0200 From: Dirk Schippers <[EMAIL PROTECTED]> To: Jocelyn Fournier <[EMAIL PROTECTED]> Cc: [EMAIL PR

Re: Query takes terribly long

2004-09-20 Thread Bill Easton
19 Sep 2004 18:35:24 +0200 From: Dirk Schippers <[EMAIL PROTECTED]> To: Jocelyn Fournier <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: Query takes terribly long No, I'm quiet sure that isn't the case as I am testing the optimized version of my website on another databas

Re: Query takes terribly long

2004-09-19 Thread Dirk Schippers
celyn Fournier www.presence-pc.com - Original Message - From: "Dirk Schippers" <[EMAIL PROTECTED]> To: "Jocelyn Fournier" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, September 19, 2004 5:49 PM Subject: Re: Query takes terribly long Hello, Indee

Re: Query takes terribly long

2004-09-19 Thread Jocelyn Fournier
ECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, September 19, 2004 5:49 PM Subject: Re: Query takes terribly long > Hello, > > Indeed, when I use {put,front,putdatetime}, no filesort is used. But the > query is still very slow. > It takes about 2 seconds. And again, mysql prefe

Re: Query takes terribly long

2004-09-19 Thread Dirk Schippers
Cc: <[EMAIL PROTECTED]> Sent: Sunday, September 19, 2004 11:55 AM Subject: Re: Query takes terribly long Hello, Sorry to bother you again, but now I have the following, bit more complicated query on the same table: SELECT id FROM story WHERE MONTH(putdatetime) = MONTH('2004-09-19&#x

Re: Query takes terribly long

2004-09-19 Thread Jocelyn Fournier
s" <[EMAIL PROTECTED]> To: "Jocelyn Fournier" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, September 19, 2004 11:55 AM Subject: Re: Query takes terribly long > Hello, > > Sorry to bother you again, but now I have the following, bit more > comp

Re: Query takes terribly long

2004-09-19 Thread Jocelyn Fournier
gt; To: "Jocelyn Fournier" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, September 19, 2004 11:05 AM Subject: Re: Query takes terribly long > Hello, > > Thanks for the hint! > With RESET QUERY CACHE, I'm always sure that the cache is empty and with

Re: Query takes terribly long

2004-09-19 Thread Dirk Schippers
quot;Jocelyn Fournier" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 18, 2004 11:37 PM Subject: Re: Query takes terribly long Hello, I added the index you said, but mysql (yes 4.x) still prefers using the other index {put,front,topcategory,approvedby}. And

Re: Query takes terribly long

2004-09-19 Thread Dirk Schippers
t;[EMAIL PROTECTED]> To: "Jocelyn Fournier" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 18, 2004 11:53 PM Subject: Re: Query takes terribly long Hello, Now this I don't understand, now the query takes only 0.05s on any of the two indexes. I di

Re: Query takes terribly long

2004-09-18 Thread Jocelyn Fournier
lyn Fournier" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 18, 2004 11:53 PM Subject: Re: Query takes terribly long > Hello, > > Now this I don't understand, now the query takes only 0.05s on any of > the two indexes. > I didn&#x

Re: Query takes terribly long

2004-09-18 Thread Dirk Schippers
rieve the row in the right order directly. Regards, Jocelyn Fournier www.presence-pc.com - Original Message - From: "Dirk Schippers" <[EMAIL PROTECTED]> To: "Jocelyn Fournier" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, Septembe

Re: Query takes terribly long

2004-09-18 Thread Jocelyn Fournier
e row in the right order directly. Regards, Jocelyn Fournier www.presence-pc.com - Original Message - From: "Dirk Schippers" <[EMAIL PROTECTED]> To: "Jocelyn Fournier" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, September 18, 2004

Re: Query takes terribly long

2004-09-18 Thread Dirk Schippers
Hello, I added the index you said, but mysql (yes 4.x) still prefers using the other index {put,front,topcategory,approvedby}. And indeed, he uses the filesort. When I force into using your index, it seems to be even slower (more rows but no filesort as you said) But I have a question about that

Re: Query takes terribly long

2004-09-18 Thread Jocelyn Fournier
Hi, You can try to add an index on (put,front,topcategory,putdatetime) to avoid MySQL has to do a filesorting on the data returned. (I assume you're using MySQL 4.x) Regards, Jocelyn Fournier www.presence-pc.com - Original Message - From: "Dirk Schippers" <[EMAIL PROTECTED]> To: <[E

Re: Query takes terribly long

2004-09-18 Thread Dirk Schippers
No, it doesn't improve the speed. I think that is because almost all rows in that table are approved. Are you also convinced that this is a very long time for such a query? Or is it normal? Andrew Kreps wrote: On Sat, 18 Sep 2004 22:25:12 +0200, Dirk Schippers <[EMAIL PROTECTED]> wrote: with