At 12:23 +0200 9/24/02, Harald Fuchs wrote:
>In article <[EMAIL PROTECTED]>,
>Daniel Kiss <[EMAIL PROTECTED]> writes:
>
>>> Question is, will this
>>> require any SQL code changes to our application? We make heavy use of
>>> features like temporary tables, autoincrement columns etc. Would if be
>>> as simple as dumping the database and restoring it to InnoDB tables?
>
>Not necessary - "ALTER TABLE tbl TYPE=InnoDB" is enough.
>
>> The simple answer is: No. You don't have to change any code in your
>> application, InnoDB will works with the actual code, because it is
>> 100% compatible with MyISAM.
>
>That's not quite right. Things that InnoDB doesn't support in
>comparison to MyISAM:
>* Fulltext indices
>* Indices on (parts of) TEXT columns
>* AUTO_INCREMENT on the second part of a combined PRIMARY KEY
>
>Any others?
OPTIMIZE TABLE
REPAIR TABLE
CREATE TABLE .... {DATA | INDEX} DIRECTORY = 'pathname'
(and several other table creation options)
symlinking
BACKUP TABLE
RESTORE TABLE
MERGE tables
Can specify initial value of AUTO_INCREMENT sequence
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
