Re: Converting table type

2004-10-31 Thread Martijn Tonies



 At 11:06 -0500 10/30/04, Michael Satterwhite wrote:
 On Saturday 30 October 2004 10:58 am, Paul DuBois wrote:
 
   What output does the following statement produce?
 
   SHOW VARIABLES LIKE 'have_innodb';
 
   If YES, the ALTER TABLE statement should have worked.
   If NO, your server doesn't have InnoDB support built in.
   If DISABLED, your server supports InnoDB but it was disable at
   startup time with --skip-innodb.
 
 That was it. Thanks. I didn't think of Debian disabling the INNODB
function.

 Rude of them. :-)

Add to that: what about raising an error/warning message
when something like that fails??

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL  MS SQL
Server.
Upscene Productions
http://www.upscene.com


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Converting table type

2004-10-30 Thread Martijn Tonies
Why not simply recreate it with the InnoDB table type?

If there's data in it, rename the old table, recreate the
table and pump the data.

All done!

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL  MS SQL
Server.
Upscene Productions
http://www.upscene.com


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Converting table type

2004-10-30 Thread Michael Satterwhite
On Saturday 30 October 2004 09:35 am, Martijn Tonies wrote:
 Why not simply recreate it with the InnoDB table type?

 If there's data in it, rename the old table, recreate the
 table and pump the data.

 All done!

Certainly that *COULD* be done, but it shouldn't be necessary (according to 
the documentation). In addition, one of the tables needing this doesn't just 
have data in it ... it has A LOT of data in it. It would not be a small, 
short running job.


pgp6Tww3k1zKJ.pgp
Description: PGP signature


Re: Converting table type

2004-10-30 Thread Martijn Tonies
Michael,

All your e-mails come as an attachment in my mailbox
instead of plain e-mail.

 Why not simply recreate it with the InnoDB table type?

 If there's data in it, rename the old table, recreate the
 table and pump the data.

 All done!

Certainly that *COULD* be done, but it shouldn't be necessary (according to
the documentation). In addition, one of the tables needing this doesn't
just
have data in it ... it has A LOT of data in it. It would not be a small,
short running job.

Well, I'm not a MySQL pro at all, but if this InnoDB
is running in its own table space, the data will have to
be transferred into there anyway.

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL  MS SQL
Server.
Upscene Productions
http://www.upscene.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Re: Converting table type

2004-10-30 Thread Paul DuBois
At 9:24 -0500 10/30/04, Michael Satterwhite wrote:
I'm running MySQL 4.0.21
In order to use Foreign Keys, I'm trying to convert a table Type to INNODB. I
issue a statement of the form
 Alter Table TblName Type=INNODB;
This statement appears to execute correctly. I would expect this to affect the
Show Create Table output, but when I say
 Show Create Table TblName;
The output still indicates MyISAM. If I add a Foreign Key with On Delete
Cascade On Update Cascade, it does not show up in the Show Create Table, and
Updating the Foreign key does not cascade to the table with the Foreign Key
Constraint.
What output does the following statement produce?
SHOW VARIABLES LIKE 'have_innodb';
If YES, the ALTER TABLE statement should have worked.
If NO, your server doesn't have InnoDB support built in.
If DISABLED, your server supports InnoDB but it was disable at
startup time with --skip-innodb.
--
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: Converting table type

2004-10-30 Thread Michael Satterwhite
On Saturday 30 October 2004 10:58 am, Paul DuBois wrote:

 What output does the following statement produce?

 SHOW VARIABLES LIKE 'have_innodb';

 If YES, the ALTER TABLE statement should have worked.
 If NO, your server doesn't have InnoDB support built in.
 If DISABLED, your server supports InnoDB but it was disable at
 startup time with --skip-innodb.

That was it. Thanks. I didn't think of Debian disabling the INNODB function.


pgpR5VPcpF3tw.pgp
Description: PGP signature


Re: Converting table type

2004-10-30 Thread Paul DuBois
At 11:06 -0500 10/30/04, Michael Satterwhite wrote:
On Saturday 30 October 2004 10:58 am, Paul DuBois wrote:
 What output does the following statement produce?
 SHOW VARIABLES LIKE 'have_innodb';
 If YES, the ALTER TABLE statement should have worked.
 If NO, your server doesn't have InnoDB support built in.
 If DISABLED, your server supports InnoDB but it was disable at
 startup time with --skip-innodb.
That was it. Thanks. I didn't think of Debian disabling the INNODB function.
Rude of them. :-)
--
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


Re: Converting table type

2004-10-30 Thread Gleb Paharenko
Hi.

I think you should upgrade to MySQL 4.0.22.





Michael Satterwhite [EMAIL PROTECTED] wrote:

 [-- text/plain, encoding quoted-printable, charset: us-ascii, 23 lines --]

 

 I'm running MySQL 4.0.21

 

 In order to use Foreign Keys, I'm trying to convert a table Type to INNODB. I 

 issue a statement of the form

 

 Alter Table TblName Type=INNODB;

 

 This statement appears to execute correctly. I would expect this to affect the 

 Show Create Table output, but when I say

 

 Show Create Table TblName;

 

 The output still indicates MyISAM. If I add a Foreign Key with On Delete 

 Cascade On Update Cascade, it does not show up in the Show Create Table, and 

 Updating the Foreign key does not cascade to the table with the Foreign Key 

 Constraint.

 

 What am I doing wrong?

 

 [-- application/pgp-signature, encoding 7bit, 8 lines --]

 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]