ODBC Import – Varchar 255 converts to Blob

[rbma]

Fields that are defined varchar 255 are being defaulted to blob during the ODBC Import. Why?

[peterlaursen]

It is an issue with the ODBC-driver, I believe!

When I for instance

1)export from Access to MySQl using the MyODBC driver

and

2)import with SQLyog using the M$ ODBC driver for Access

… I won't always get the same datatypes

But then SQLyog/SJA has the “transform” option that let's you choose char/varchar/BLOB/TEXT and set length of imported variables as you want.

Which DB are you importing from and to and which ODBC driver do you use ?

[rbma]

peterlaursen wrote on Jul 29 2005, 05:56 PM:

It is an issue with the ODBC-driver, I believe!

When I for instance

1)export from Access to MySQl using the MyODBC driver

and

2)import with SQLyog using the M$ ODBC driver for Access

… I won't always get the same datatypes

Timestamp is also affected.

peterlaursen wrote on Jul 29 2005, 05:56 PM:

Which DB are you importing from and to and which ODBC driver do you use ?

MSSQL to MySQL.

ODBC driver that came with Windows XP

[peterlaursen]

Quote:

Timestamp is also affected.

But if you use the TRANSFORM facililty of SQLyog and choose MySQL TIMESTAMP datatype, will it then import correct ?

I don't know how a TIMESTAMP is stored internally in MS SQL. In MySQL it is stored as a string.

If the ODBC-driver does not tell SJA that variable is a TIMESTAMP, you'll have to!

The ODBC-driver for MS-ACCESS works fine with SQLyog and DATE, TIME, DATETIME and TIMESTAMP variables.

[Author]

Posts