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

CSV import

forums › forums › SQLyog › SQLyog Comments › CSV import

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • August 17, 2004 at 10:59 am #8533
      3rdvalve
      Member

      So I import a csv sheet using the csv import. But every row ends up with the entire record in the first field!

      On further investigation, I see that yog defaults to ' t ' as the field separator. Why? CSV means “COMMA separated values” and therefore the separator is a comma – by definition.

      By all means have a generic text file import where you expect to set field and record separators, but CSV has GOT to be COMMA! 😮

    • August 17, 2004 at 11:36 am #16186
      Shadow
      Member

      Technicly you are right, it was Excel that introduced this sluggish terminology (Excel treats all text files that have some data separation as csv), SQLyog merely follows this routine. One should check the settings, however, before performing any operation. BTW, SQLyog notes your settings, so next time comma will be offered as field separator.

    • August 17, 2004 at 11:51 am #16187
      3rdvalve
      Member

      I can well believe MS was behind the confusion somewhere. 😉

      Now I know to actually READ the dialog box, I probably won't make the same mistake again (?)

      But it's great to know SQLyog will save the last setting…

    • August 17, 2004 at 1:13 pm #16188
      Shadow
      Member
      Quote:
      I can well believe MS was behind the confusion somewhere.

      I don't think they were the only one, but not surprising at all 🙄

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