I am not sure how the conversion is done, but if it dumps the data,
renames the old file,
loads the new file, and deletes the dump and old file, it would need
freespace twice the
size of the current table and index.
Hang wrote:
>
> Thanks!
>
> So, is there any way to calculate the approximate
Alternate solution,
mysqldump --add-droptable db_name table_name >
path/with/a/lot/of/room/table_name.sql
Edit your file and change the table create clause to include TYPE = MYISAM
after the column defs. Ie:
CREATE TABLE table_name (column1 def, column2 def,...) TYPE = MYISAM
Then: mysql dbname
Hi.
On Thu, Mar 29, 2001 at 10:47:54AM +0800, [EMAIL PROTECTED] wrote:
> Thanks!
>
> So, is there any way to calculate the approximate disk space required for the
>transformation
> from ISAM to MYISAM?
I would have assumed 330MB and don't see the reason why it should use
more. Obviously I am w
Thanks!
So, is there any way to calculate the approximate disk space required for the
transformation
from ISAM to MYISAM?
Gerald Clark wrote:
> error 28 is "No space left on device".
>
> Hang wrote:
> >
> > Greetings,
> >
> > I am upgrading my mysql from 3.22.23b to 3.23.35 on RedHat with kern
error 28 is "No space left on device".
Hang wrote:
>
> Greetings,
>
> I am upgrading my mysql from 3.22.23b to 3.23.35 on RedHat with kernel
> 2.4.0. I followed the instructions on the manual for the upgrade. Every
> goes fine except I can't convert one table from ISAM to MYISAM.
>
> I got qu
Greetings,
I am upgrading my mysql from 3.22.23b to 3.23.35 on RedHat with kernel
2.4.0. I followed the instructions on the manual for the upgrade. Every
goes fine except I can't convert one table from ISAM to MYISAM.
I got quite a lot of tables and all can be converted successfully but
not this
