Hi Mike,
I upgraded to 1.0.13 and it works as expected
(see
http://forums.mysql.com/read.php?104,37366 for problems during upgrade).
On a sidenode, I'm extremely happy with the current results.
Now the next problem arises:
The MT shows several tables (~120) that require manual editing because of MySQL errors during migration.
Almost all errors are caused by an invalid type for some table row, as seen in this fake snippet of the CREATE logfile:
----------------------------------------
CREATE TABLE `foo`.`bar` (
[...]
`asdf` (nil) NULL,
[...]
)
ENGINE = INNODB;
----------------------------------------
In the corresponding Oracle database, these rows always have a relatively large size, such as NUMBER(100) or FLOAT(126).
My guess is the MT assigns the type "(nil)" to rows with sizes larger than some MAX_VAL.
Our current approach consists of a Perl script which simply replaces "(nil)" with "VARCHAR(255)" in the Creates.sql logfile, which seems to fit our purpose at this time.
Anyway, is this a known issue? Will it be fixed sometime soon?
Greets,
Philip