List:General Discussion« Previous MessageNext Message »
From:Egor Egorov Date:August 16 2002 3:53pm
Subject:Re: Is this a known issue?
View as plain text  
Song,
Friday, August 16, 2002, 12:57:58 AM, you wrote:

S> Well, I am not sure if anyone has experienced the same problem, or if this
S> problem has been documented, but this is what I have noticed:

S> After one of my data table was full, I started to delete old records from
S> the table to allow new data to be inserted. Since then, the LIMIT function
S> stop working. I used to be able to do:

S> SELECT * FROM mytable LIMIT 0, 50

S> or

S> DELETE FROM mytable LIMIT 0, 50

S> Now it doesn't work any more. I have to add a WHERE clause in order to make
S> the LIMIT working. For instance:

S> SELECT * FROM mytable WHERE id > 0 LIMIT 0, 50

S> or

S> DELETE FROM mytable WHERE id > 0 LIMIT 0, 50

S> However, this is not a good query considering 15 million records in the
S> table. I have repeated the same problem on two systems with similar setting.

Run CHECK TABLE table_name to know if the table is not crushed.





-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   Egor.Egorov@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
       <___/   www.mysql.com


Thread
Is this a known issue?Jay Song16 Aug
  • Re: Is this a known issue?Jocelyn Fournier16 Aug
  • Re: Is this a known issue?Egor Egorov16 Aug
RE: Is this a known issue?Jay Song16 Aug