Unsupported Screen Size: The viewport size is too small for the theme to render properly.

ODBC Import Problems and Suggestions

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › ODBC Import Problems and Suggestions

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • February 24, 2004 at 2:04 pm #8342
      Smeagle
      Member

      Hi,

      found another glitch when importing from MSSQL to mySQL:

      – Datatype “BIN” is converted to “char(1)”. should be “BOOL”.

      – Datatype “VARCHAR(>254)” is converted to “BLOB(>254)”. Should be just “BLOB” or better “TEXT”, als BLOB(size) is not valid.

      Suggestions for ODBC Import:

      – I would like to be able to save settings of Import… I import a large/complex database often and would like to save the manual settings, like selection of tables and conversion for datatypes…

      – I would like to setup a “override table” for datatype-conversion… f.e. I would prefer to import “BIN” as “TINYINT”…

      Thanks,

      – Oliver

    • February 24, 2004 at 4:46 pm #15510
      Ritesh
      Member

      Hmmm….

      Thanks for the feature request.

    • March 15, 2004 at 4:55 pm #15511
      billprozac
      Member

      I can second this! I would love to be able to store these common imports. I would also like the abilty to execute the imports either from cli or through a built in job scheduler. I have an antiquated SQL database that I runa SQL statement on which exports to a flat file then I am importing into the MySQL. THis would save a few steps and eliminate the need for the flat file in the middle and would allow me to schedule the update to occur every hour.

  • Author
    Posts
Viewing 2 reply threads
  • You must be logged in to reply to this topic.