Re: Converting MyISAM to InnoDB

2002-03-13 Thread ImpactNET - Edgar R Gutierrez
data. I also set my MySQL server so that it create InnoDB tables by default. MySQL is currently in the processing of constructing the tables.looks like...the problem has been solved! Thanks - Original Message - From: ImpactNET - Edgar R Gutierrez <[EMAIL PROTECTED]> To: Heikki

Re: Converting MyISAM to InnoDB

2002-03-13 Thread ImpactNET - Edgar R Gutierrez
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! &

Re: Multiple Column Keys with Auto Increment

2002-03-13 Thread ImpactNET - Edgar R Gutierrez
0B0B1 This works if my table is MyISAM. It doesn't work in InnoDB... I hope there is a solution... Thanks again! - Original Message - From: BD <[EMAIL PROTECTED]> To: ImpactNET - Edgar R Gutierrez <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Se

Converting MyISAM to InnoDB

2002-03-12 Thread ImpactNET - Edgar R Gutierrez
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

Multiple Column Keys with Auto Increment

2002-03-12 Thread ImpactNET - Edgar R Gutierrez
Greetings!!! I would just like to know if the following is normal: I created a file TRANSACTION_LOG.sql to create an InnoDB table with MULTIPLE KEYs with one AUTO COLUMN. The file consists of the following SQL commands: drop table TRANSACTION_LOG; create table TRANSACTION_LOG (SESSION_ID int(1