I'm not sure it has to do with the number of rows, but in any case this is what happened:
mysql> select count(*) from email_body; +----------+ | count(*) | +----------+ | 208853 | +----------+ 1 row in set (0.00 sec) mysql> alter table email_body MAX_ROWS=700000; Query OK, 315 rows affected (0.23 sec) Records: 315 Duplicates: 0 Warnings: 0 mysql> select count(*) from email_body; +----------+ | count(*) | +----------+ | 319 | +----------+ 1 row in set (0.00 sec) Your suggestion seemed to wipe out my rows ! (s'ok I got a backup ;p) -- Keith Bussey Wisol, Inc. Chief Technology Manager (514) 398-9994 ext.225 Quoting "Keith C. Ivey" <[EMAIL PROTECTED]>: > On 4 Sep 2003 at 10:13, Keith Bussey wrote: > > > -rw-rw---- 1 mysql mysql 4.0G Aug 31 01:01 email_body.MYD > > > > Thus if I try and insert one more row I get the error: > > > > ERROR 1114: The table 'email_body' is full > > By default, MyISAM tables use 4-byte pointers to indicate positions > in the data file. So if your data file gets bigger than 4 GB (or > larger for fixed-length records, but that's not what you have), you > get that error: > > http://www.mysql.com/doc/en/Full_table.html > > Figure out how many records you're likely to need and do > > ALTER TABLE email_body MAX_ROWS=<whatever>; > > -- > Keith C. Ivey <[EMAIL PROTECTED]> > Tobacco Documents Online > http://tobaccodocuments.org > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
