Problem in ODBC-Import

[Smeagle]

Hiya,

when importing tables from MSSQL, a “varchar” type larger than 255 bytes is imported as “blob (length)” which is not valid syntax. And I think the more obvious choice for large varchars would be “text” instead of “blob”. What do you think?

If I replace “blob(xxx)” with “text” it seems to work.

Thanks,

– Oliver

[Shadow]

You may remove the length (xxx) from the definition, just leave the BLOB.

[Smeagle]

Hiya,

I know, it works when I change the “blob(xxx)” to “text”. It would also work with “blob”, but as the original datatype was “varchar”, I set it to “text”. But I import a _large_ dump from ms sql to mysql often, and it's not nice to have to do this everytime “by hand”…

– Oliver

[Shadow]

It could be a feature request: SQLyog should watch out for such columns and do a silent column type change or could ask the user what to do. Of course, SQLyog should pay attention to the size of the field and do the conversion accordingly (tinyblob, blob…).

TEXT and BLOB fields are essentially the same in MySQL…

[Smeagle]

Hello!

is there a solution? I have to do this every morning. I have to split the import into severel “.sql”s and have to edit them one after another. As we are talking about a database with ~500MB, this takes some time.

I would like to simply start an import directly into mysql, that is not possible now.

Please!

– Oliver

[Smeagle]

Ups,

just noticed, there is a new version… Tried it, and: it works!

Thanks,

– Oliver

[Ritesh]

Great 🙂

[Smeagle]

Hmm,

🙁

I have to correct myself:

It still isn't working. Last time I forgot to delete the original database, so the table structure was reused.

If I import into a empty database, sqlyog still converts “varchar(>254)” to “blob (>254)”

This will not work. I would suggest to use “text” or “blob” (without length) for varchars with more than 254 characters length.

– Oliver

[Author]

Posts