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

Sqlyog Import Problem

forums forums SQLyog SQLyog: Bugs / Feature Requests Sqlyog Import Problem

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #33221
      peterlaursen
      Participant

      The problem is undoubtedly a variant of this one:

      http://www.webyog.co…-in-sqlyog.html

      .. and as such a problem with thow you store data in your database.

      Now please tell:

      1) How was the SQL-dump created? With SQLyog 5.x or 9.6x or another application? Does the import job create the tables of did they exist in advance?

      2) How is the dump file encoded?If it is UTF8 please open the dump in Notepad or any utf8-enabled editor and check if the accented characters display correctly here?

      You are welcome to create a private ticket by sending a mail to support@webyog,com. We wil need to see some sample data/scripts and you may not want to exchange them in public.

    • #33222
      peterlaursen
      Participant

      We also need the result of “SHOW GLOBAL VARIABLES LIKE '%char%';” from the server.

    • #33223
      peterlaursen
      Participant

      And finally please read:

      http://www.webyog.co…y-language.html

      “However if you execute a SQL-script from a file you may include a SET NAMES statement in that file. You will need to do if character data in the file are not encoded with the server default charset. When SQLyog executes an external file, a separate connection is created for that and SET NAMES in that file will not affect the connection that the GUI uses. SQL scripts generated by SQLyog are UTF8-encoded and the file contains a “SET NAMES utf8″ statement. But if the script is generated with another program it is not necessarily the case.”

      So does the script/dump contain a SET NAMES statement on top matching how data are encoded in the file?. As far as I remember SQLyog before 6.0 did not add a SET NAMES statement to SQL-dumps and the data in the dump was encoded 'as returned by the server' and the file was ANSI encoded. (unlike from 6.0 where file and data are always UTF8 encoded in SQLyog dumps and there is a SET NAMES UTF8 on top).

      Please share a complete table dump with us to [email protected] (you may strip a lot of data as long as only one row is there where the problem is reproducible).

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