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

another import issue from sybase

forums forums SQLyog Sync tools, Migration, Scheduled Backup and Notifications another import issue from sybase

  • This topic is empty.
Viewing 1 reply thread
  • Author
    Posts
    • #8511
      dubh
      Member

      I'm not sure whether this one is a bug or a feature – but it's definitely a difference in behaviour from SQLYog 3.11 to SQLYog 3.71.

      For reasons best known to I'm not sure who, datetimes in the Sybase database I'm importing from are varchars formatted as follows:

      2004-07-26 15:39:25.031

      In SQLYog 3.11, either by doing an import query through ODBC or a table import through ODBC this exact formatting is preserved.

      But in SQLYog 3.71, an import query through ODBC preserves the formatting, but a table import through ODBC does not. Instead, the nicely formatted varchar, which otherwise could be used as a datetime in all the queries I've tried, turns into this:

      20040726153925

      This wouldn't be so bad, except my table of extracted data now contains some well-formatted stuff from when I was using 3.11, and some crap formatted stuff from when I started using 3.71.

      This is very frustrating. What can I do?

      <_<

    • #16121
      dubh
      Member

      I've found what the difference in behaviour seems to be between the two versions of SQLYog. When slurping in entire tables, the default format for the dates imported seems now to be a “timestamp”; whereas previously it was a “Datetime”. This can be corrected at import, fortunately.

Viewing 1 reply thread
  • You must be logged in to reply to this topic.