OK,
I found out, why the table grows that extraordinary.
After
'CREATE TABLE new_1 SELECT * FROM output_1';
All columns of new_1 are CHAR(255) instead of VARCHAR(255) like in output_1
( see below).
Now my simple questions are:
1. Why , I saw something about silent changes in the docs,
Dear Ladies and Sirs,
I have a problem to create a tables duplicate with:
CREATE TABLE new_1 SELECT * FROM output_1;
The table output_1 has this structure:
Field TypeNullKey
af_1int(11) YES MUL
af_3varchar(255)YES
It seems that you have reached the 2G file limit with many Linux system. I
am not familiar with SuSe. As I know, you may try to use raid option. You
may refer to MySQL doc. on 'create' for details.
KH
Dear Ladies and Sirs,
I have a problem to create a tables duplicate with:
CREATE
Hi Chiu,
It seems that you have reached the 2G file limit with many Linux system. I
am not familiar with SuSe. As I know, you may try to use raid option. You
may refer to MySQL doc. on 'create' for details.
Yes I know, that I can just manage files to 2 GB.
The question was, why is the new
Compare tables with :
=show create table t1;
=show create table t2; Check table type.
Or use dump command from shell:
shellmysqldump -pPassword --user=username db_name t1 t1.sql
mysqlrename table t1 to t2;
shellmysql -pPassword --user=username t1.sql db_name
Or try to set MIN_ROWS =
Use BIGINT
use altertable ...that will take a week
Russell Griechen
- Original Message -
From: Franz, Fa. PostDirekt MA [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 24, 2003 2:35 AM
Subject: Strange BUG? with a working table
Dear Ladies and Sirs,
I have a problem