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

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
    Posts
  • in reply to: Sqlyog_dump_000.dmp Created While Dumping As Sql #24221
    Lexx918
    Member

    Done

    in reply to: Sqlyog_dump_000.dmp Created While Dumping As Sql #24219
    Lexx918
    Member

    Where to send the dump? There's one!

    / SQLYog Ultimate, v11.2, 64-bit, Win7 /

    in reply to: Encoding Problem After Reconnect #32808
    Lexx918
    Member
    'peterlaursen' wrote:

    ..you can now enter SET NAMES UTF8

    COOL! It works! 🙂

    Tnx!

    in reply to: Encoding Problem After Reconnect #32804
    Lexx918
    Member
    'peterlaursen' wrote:

    Can you explain me how such a user (having only USAGE privilege and not SELECT privilege to any table at all) is able to SELECT anything at all? The original problem was about cyrillic letters garbling, right?

    I do not know the details USAGE/SELECT/GRANTS, etc., but: http://dev.mysql.com/doc/refman/5.1/en/show-grants.html

    Quote:
    SHOW GRANTS requires the SELECT privilege for the mysql database.

    So to this I have the right!

    Yes, the problem is in cyrillic.

    in reply to: Encoding Problem After Reconnect #32802
    Lexx918
    Member
    'peterlaursen' wrote:

    Most often SQLyog will connect as a user with SUPER privilege.

    SHOW GRANTS FOR CURRENT_USER();

    GRANTS FOR [email protected].5.0/255.255.255.0


    GRANT USAGE ON *.* TO 'myname'@'192.168.5.0/255.255.255.0' IDENTIFIED BY PASSWORD '*…'

    in reply to: Encoding Problem After Reconnect #32801
    Lexx918
    Member
    'peterlaursen' wrote:

    Are you perfectly sure that it does not work with SQLyog after reconnection?

    Yes. The administrator has removed the option '-skip..' and added the option '-init..'. Restart the server.

    Then we checked the text on the site – everything is fine.

    Then I repeated the SELECT + KILL + SELECT in SQLYog – all bad! Reconnect is, but the answer came broken.

    That is, seen as an option '-init..' (without the option '-skip..') affect the text on the site. In SQLYog no difference.

    in reply to: Encoding Problem After Reconnect #32798
    Lexx918
    Member

    There is also an option: http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_init_connect

    [mysqld]

    init_connect = 'SET NAMES cp1251'

    And it worked for php! But not in SQLYog.

    in reply to: Encoding Problem After Reconnect #32797
    Lexx918
    Member

    Thank you. We think!

    A link can be published. I do not mind.

    Maybe someone even notice the word “Dota” in my profile, and to dare to play with me!

    in reply to: Encoding Problem After Reconnect #32795
    Lexx918
    Member
    'peterlaursen' wrote:

    1) I do not understand.

    sql-yog.png

    Now all settings are in the configuration file database.

    All clients (SQLYog, php, phpMyAdmin, MySQL Workbench, etc.) work with the option “skip-character-set-client-handshake”. And do not SET NAMES. The first diagram in Fig.

    If I remove that option, all clients will have to put SET NAMES after connecting. The second scheme in Fig.

    Why do I need to make two requests during the connection in php, if I make one?

    in reply to: Encoding Problem After Reconnect #32793
    Lexx918
    Member

    1.

    If I remove that option, then I have to do SET NAMES in the code after each connection. Otherwise, the DBMS gives “??? ?? ???”.

    We think that the decision in the configuration file more concise.

    2.

    You did not answer, why does SQLYog SET NAMES after the first connection and does not do after the other: http://www.webyog.com/forums/index.php?showtopic=6301&st=0&p=26082&#entry26082

    in reply to: Encoding Problem After Reconnect #32788
    Lexx918
    Member
    'peterlaursen' wrote:

    Is it still a Percona Server?

    Yes, of course.

    settings [mysqld]:

    skip-character-set-client-handshake

    character-set-server=cp1251

    collation_server=cp1251_general_ci

    in reply to: Encoding Problem After Reconnect #32786
    Lexx918
    Member
    'peterlaursen' wrote:

    Since we have already spent quite a lot of time with no success on this I will have to ask you to upgrade the server (to PerconaServer version: 5.1.60-rel13.1 at least) or set it up on another similar system. Next check if the problem is still reproducible.

    We have updated the server. Now his version 5.5.19-55. It did not help.

    in reply to: Encoding Problem After Reconnect #32784
    Lexx918
    Member

    Add detailed logging operations, trace execution, creation of dumps, etc.

    I'm sure you can track the time of receipt of an invalid response from the server. Or incorrect data output to the user.

    in reply to: Encoding Problem After Reconnect #32782
    Lexx918
    Member
    in reply to: Encoding Problem After Reconnect #32779
    Lexx918
    Member
    'peterlaursen' wrote:

    I am 99.9 sure that ..

    We use MySQL Percona Server 5.1.52.

    The code base is no different from the main mysql.

    Bug has been fixed (even in 5.1.12).

    In other programs, no problem: I tried to repeat the bug in MySQL Workbench 5.2.35 CE – no problems after a reconnect. The console also no anomalies. Only in SQLyog.

Viewing 15 posts - 1 through 15 (of 18 total)