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

In Export

forums forums SQLyog Using SQLyog In Export

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • #12265
      malik
      Member

      Hi

      I am exporting to csv and i am getting more rows in the exported csv file than is visible in sqlyog/thedatabase.

      See attached.

      Any ideas what is causing this and how to resolve.

      Many Thanks

    • #31989
      peterlaursen
      Participant

      This is probably because of the escaping settings not working well with actual data in the table. Do you have “” (backslash character) or linebreaks in the data for instance? Also are you importing using LOAD DATA syntax when importing or are you using the ODBC-based option?

      It is very difficult to comment on without exact data for the table. Can you share the CSV-file? If you want privacy send a mail to [email protected] and attach the file (it will create a support ticket). Also a SQL export from the table will be useful.

      Edit/Added: First step should be to find out if this happens during export or during import. That is why we need the CSV-file. But best of all would be if you could 'compose' an example with only a few rows in the table where this is reproducible.

    • #31990
      malik
      Member
      'peterlaursen' wrote:

      This is probably because of the escaping settings not working well with actual data in the table. Do you have “” (backslash character) or linebreaks in the data for instance? Also are you importing using LOAD DATA syntax when importing or are you using the ODBC-based option?

      It is very difficult to comment on without exact data for the table. Can you share the CSV-file? If you want privacy send a mail to [email protected] and attach the file (it will create a support ticket). Also a SQL export from the table will be useful.

      Edit/Added: First step should be to find out if this happens during export or during import. That is why we need the CSV-file. But best of all would be if you could 'compose' an example with only a few rows in the table where this is reproducible.

      Hi Peter

      The import files do have line breaks.

      The files are .txt files containing rows of data (comma delimit):

      xxxx,xxx,xxxxx,xxxx,xxx,xxx,xxxxx

      xxxx,xxx,xxxx,xxxx,xxxxx,xxxxx,xxx

      xxx,xxxxx,xxxxxx,xxxx,xxxxx,xxx,xxx

      All loaded using sqlyog LOAD DATA

      Any ideas?. If not i will have to do as you say and begin more detailed troubleshooting and find a small reproduceable sample I can post.

    • #31991
      peterlaursen
      Participant

      Please provide an exact example (table dump, CSV-file). But if data has linebreaks in string columns try to avoid the “” character for CSV-metadata. Use ” # ” or ” ยค ” or” &” or ” | ” or whatever (both when exporting and importing) instead.

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