ssage.
Regards,
Gavin Towey
-Original Message-
From: Steve Staples [mailto:sstap...@mnsi.net]
Sent: Monday, February 08, 2010 9:39 AM
To: mysql@lists.mysql.com
Subject: Converting MyISAM to InnoDB
Hello again!
I am trying to convert my tables to InnoDB, and i am getting an error...
Error:
Hello again!
I am trying to convert my tables to InnoDB, and i am getting an error...
Error: 1075
Incorrect table definition; there can be only one auto column and it must be
defined as a key
Now, I converted a table in my sandbox earlier this morning to do some
testing, and it worked fine... mi
]>
To: "Cliff" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, March 05, 2004 10:16 AM
Subject: Re: Major problem converting MyISAM to InnoDB
> Cliff wrote:
> > I think I may have gotten closer to the root of the problem. It seems
that
> > the field nam
Cliff wrote:
I think I may have gotten closer to the root of the problem. It seems that
the field named 'comments' is the one that crashes the server when it is
selected. Here is the output of the logs when I do 'select comments from
allusa':
040304 23:14:52 mysqld restarted
040304 23:14:53 InnoD
Discussion« Previous MessageNext Message »
From: Cliff Date: March 5 2004 8:12am
Subject: Re: Major problem converting MyISAM to InnoDB
I think I may have gotten closer to the root of the problem. It seems that
the field named 'comments' is the one that crashes the server when it is
selected. H
: Thursday, March 04, 2004 1:24 PM
Subject: Re: Major problem converting MyISAM to InnoDB
> Cliff,
>
> - Original Message -
> From: ""Cliff"" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.myodbc
> Sent: Thursday, March 04, 2004 7:07 PM
&g
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 04, 2004 1:24 PM
Subject: Re: Major problem converting MyISAM to InnoDB
> Cliff,
>
> - Original Message -
> From: "&q
Cliff,
- Original Message -
From: ""Cliff"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, March 04, 2004 7:07 PM
Subject: Re: Major problem converting MyISAM to InnoDB
> Hi, I ran CHECK TABLE with the EXTENDED option on the table a
> Hi, I ran CHECK TABLE with the EXTENDED option on the table and it reports
> everything ok:
>
> mysql> check table allusa extended;
> +---+---+--+--+
> | Table | Op| Msg_type | Msg_text |
> +---+---+--+--+
> | bb.allusa | check | s
nal Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 04, 2004 12:36 AM
Subject: Re: Major problem converting MyISAM to InnoDB
> Cliff,
>
> please run
>
> CHECK TABLE ...
>
> on your table and look if mysql
, March 04, 2004 7:18 AM
Subject: Re: Major problem converting MyISAM to InnoDB
> Cliff wrote:
> > Recently I tried to convert our largest table from MyISAM to InnoDB.
During
> > the process I believe there was a problem where something was corrupt
along
> > the way. It was s
Cliff wrote:
Recently I tried to convert our largest table from MyISAM to InnoDB. During
the process I believe there was a problem where something was corrupt along
the way. It was stupid, but I did not verify that our backup system was
working correctly, since I assumed it had been running as usua
Recently I tried to convert our largest table from MyISAM to InnoDB. During
the process I believe there was a problem where something was corrupt along
the way. It was stupid, but I did not verify that our backup system was
working correctly, since I assumed it had been running as usual. It was not
Hi Matt. Thanks a lot again !
It worked pretty good.
There is no problem about the app, because
the use of the indexes is in charge of the DBMS (MySQL). The
app "doesn't know" about the tables and indexes details.
Best Regards,
Fred.
> Hi Fred,
>
> Also, you may be able to swap the or
3, 2004 6:11 PM
Subject: Re: Converting MyISAM to InnoDB type.
> Hi Matt and thank you very much
>
> Now I get the point I'll have to decide if I maintain these
> two tables in MyISAM or if I drop the AUTO_INCREMENT and
> change the source-code in Delphi.
>
> It&#x
Hi Matt and thank you very much
Now I get the point I'll have to decide if I maintain these
two tables in MyISAM or if I drop the AUTO_INCREMENT and
change the source-code in Delphi.
It's clear now that the problem is the lack of support of InnoDB.
Thanks for your help and regards,
Fre
"Fred"
Sent: Saturday, January 03, 2004 5:38 PM
Subject: Re: Converting MyISAM to InnoDB type.
>
>
> >
> > If you change the Type=MyISAM to Type=InnoDB and execute the
> > create query, what message do you get?
> >
>
> Hi you all .. again
&g
Tuuri <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 14, 2002 8:08 AM
Subject: Re: Converting MyISAM to InnoDB
> Hi there,
>
> I just created an InnoDB table mirroring the schema of the original
table...
>
> But, I am getting the following...
>
&
ABLE (MYD +MYI) is ~ 150MB
- Original Message -
From: Heikki Tuuri <[EMAIL PROTECTED]>
To: "ImpactNET - Edgar R Gutierrez" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, March 13, 2002 9:15 PM
Subject: Re: Converting MyISAM to InnoDB
> Hi!
&
://www.innodb.com for the online manual and latest news on InnoDB
-Original Message-
From: "ImpactNET - Edgar R Gutierrez" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Date: Wednesday, March 13, 2002 9:25 AM
Subject: Converting MyISAM to InnoDB
>
>Hello,
>
Hello,
We are currently in the process of converting our MyISAM tables to InnoDB to
make our tables
transaction safe. Unfortunately, I am getting the following error on one
of the tables...
mysql> alter table SUBSCRIBERS type = InnoDB;
ERROR 1114: The table '#sql-fcc_1' is full
mysql>
What v
21 matches
Mail list logo
