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

Text Import

forums › forums › SQLyog › Using SQLyog › Text Import

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • August 23, 2011 at 5:55 pm #12429
      Ward C
      Member

      I have a large cvs file with account information, when using the import utility from scratch, it deems one column as type int.

      This column has numbers up to 9999999999 which falls short of a 10 digit int field.

      I have changed the import to use double, varchar , number, etc, no matter what I use, any number greater than 2144200001 gets converted to null.

      Any ideas on why this is happening? why it seems to treat it as an integer field no matter what is selected?

    • August 23, 2011 at 8:45 pm #32573
      peterlaursen
      Participant

      Please try to map the column to a BIGINT during import.

    • August 24, 2011 at 12:54 pm #32574
      Ward C
      Member
      'peterlaursen' wrote:

      Please try to map the column to a BIGINT during import.

      I have tried that as well, even varchar 24, only imports up to that number, which is odd.

      It is almost like it auto detects the column as int and will not override.

      I have tried a numeric 17 zerofill.. and still yet that is the highest.

      when opened with excel the largest number is 99380000001

      Just for saying, the other columns that it detects as double does not seem to have this problem. This column which is auto detected as INT seems to be an issue.

    • August 24, 2011 at 1:45 pm #32575
      peterlaursen
      Participant

      Looks like an issue with the (Microsoft text-) ODBC driver then. We will have to check this.

      But you could try to import using LOAD DATA syntax. Note that in that case the table structure must be created in advance.

    • August 24, 2011 at 1:55 pm #32576
      Ward C
      Member
      'peterlaursen' wrote:

      Looks like an issue with the (Microsoft text-) ODBC driver then. We will have to check this.

      But you could try to import using LOAD DATA syntax. Note that in that case the table structure must be created in advance.

      I have done this with the table structure created in advance as well.. (ran once to create) modified table and then used to re-import.

      I was thinking that it might be the driver.

      but as I said even just changing column to varchar never solved the import itself. seems something is converting it to signed INT before INSERT

      The data is not that critical to me as someone else is importing into oracle for a work around, but just thought someone should know to take a look at what is wrong.

      Thanks, LOAD DATA worked fine.

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