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 15 total)
  • Author
    Posts
  • in reply to: Sqlyog 12.1 Flat Design #35288
    zef
    Member

    Thank you.

    in reply to: Sqlyog 12.1 Flat Design #35286
    zef
    Member

    Is there any way to set a background color for line numbers in the Query Editor?

     

    It is very distracting, when I am not able to see where is a zero position in editor line.

    in reply to: Pasting Statements Shorcuts #31604
    zef
    Member
    'ashwin' wrote:

    Hi,

    Can you tell the exact SQLyog version you are using?

    8.71 Community

    It is about the editor behavior.

    Maybe this picture tells more

    in reply to: #28268
    zef
    Member

    I have tried to edit my UTF8 and CP1250 data and everything looks OK.

    Thank you very much.

    in reply to: #28266
    zef
    Member
    peterlaursen wrote on Jan 28 2009, 12:41 PM:
    @zef .. please tell: are you a COMMUNITY or ENTERPRISE user?

    Community

    in reply to: #28263
    zef
    Member
    peterlaursen wrote on Jan 27 2009, 11:07 AM:
    @zef – please tell: does the file you provided display OK in Notepad on your system (with Slovak regional settings) ?

    Yes. Screenshot attached.

    in reply to: #28260
    zef
    Member
    'peterlaursen' wrote on 'Jan:

    MySQL Query Browser does not understand these data either!

    (but I do not claim to be an expert with that program)

    I believe in this case it is probably just used font problem

    My screenshot enclosed.

    in reply to: #28259
    zef
    Member
    Quote:
    What application stored those data? Did this application SET charset parameters (like SET NAMES etc.) properly?

    It is a PHP script which generates HTML in windows-1250 and uses SET NAMES cp1250 (for historical reasons)

    Could this cause the problem?

    Quote:
    Anyway try to store some local strings with SQLyog (it does SET NAMES properly!)

    I have tried to TYPE (no copy-paste to avoid charset problem, no set names) to the SQLyog the folloving statement:

    insert into test3 (test)

    values ('Pôvodná požiadavka od: Martin Lichman Che DE 23.01.2009 10:23nefunkčný HDD. Nebutuje z HDD ale zo siete.rnrnPC HP Compaq d330 P4 2.4GHz, PN:DG306A, nie je v záruke.rnDisk IDE 40GB alebo iný s vyššou kapacitor.rnSúrne.rnDisk doručiť na OIKT.rnDakujem. ');

    Data in table are OK. They are OK in the PHP application. They are also DISPLAYED CORRECTLY in SQLyog's grid.

    But they are displayed WRONG in the BLOB editor.

    But when i shortened the string to 202 characters:

    insert into test3 (test)

    values ('Pôvodná požiadavka rnod: Martin Lichman Che DE 23.01.2009 10:23rnnefunkčný HDD. Nebutuje z HDD ale zo siete.rnrnPC HP Compaq d330 P4 2.4GHz, PN:DG306A, nie je v záruke.rnDisk IDE 40GB alebo in');

    Data in table are OK and DISPLAYED CORRECTLY in the BLOB editor too.

    I do not understand.

    in reply to: #26855
    zef
    Member

    Just a small feature suggestion:

    Maybe SQLyog could display wanings automaticaly if any appear as a result of a executed statement.

    in reply to: #26853
    zef
    Member

    thank you

    in reply to: #25668
    zef
    Member

    Seems good, thank you.

    in reply to: #25664
    zef
    Member

    I am not complaining about statement. This is ok.

    The problem is purely grafical. 🙂

    See screenshot.

    in reply to: #25662
    zef
    Member

    > First you write server version 5.0.51 and next you write server version 5.0.37. Do you have more servers?

    Yes, I have WXP with 5.0.51 and W2000 with 5.0.37. Sorry for confusion.

    > CHARSET parameter in LOAD DATA is supported from server version 5.0.38 only! For that reason that option is disabled in SQLyog if server version is lower (server would return an error!9.

    I had no idea it could be such a new.

    > Actually we tested on an old machine that had an old server version and that is why we thought tehre was a bug. Now it does not seem so.

    It works for us with Win 2k and MySQL 5.0.45.

    Can you reproduce with Win2K and servers >= 5.0.38? There may be some bug/regression in the 5.0.51 server then!

    I just have tried it on W2000 and 5.0.51 and it works.

    Import of UTF8 csv file offers right charset utf8 and works fine.

    Thanks!

    Just a minor cosmetic issue:

    When I try import CSV with charset cp1250, the offered charset is [default]

    Clicking on the input probably shows the list of available charsets, but the height of the list is zero (showing just black line).

    I can choose right charset only with keyboard arrows, or mouse wheel, not by mouse click.

    in reply to: #25658
    zef
    Member

    > what is your OS?

    Windows 2000 service pack4, Czech version.

    > any other idea?

    maybe Community edition vs. Enterprise?

    > Are you sure the file is a text file and not a binary file?

    The file I am trying to import is the same as enclosed to my first post.

    > Anyway I have another issue with RC2. This dialogue pops up when I select 'import from csv'.

    reason is of course that the last file used does not exist any more.

    I do not have this issue. Neither in case the last used file does not exist.

    > what is your LOCALE setting? Czech, Slovenian, Polish … ?

    Slovak

    > if it happens with specific files please zip and att,ach an example.

    No, I tried several files, different codepages. The same behavior.

    > 1)does the CREATE/ALTER TABLE dialogues display charsets?

    > 2)what does “select * from information_schema.character_sets” return?

    yes, screenshots attached

    > This may be a server issue (that we have seen similar some times when a 5.x server has been installed on top of a previous version and this upgrade was done incorrectly).

    This one is version 5.0.37, clean instalation, no upgrade.

    in reply to: #25654
    zef
    Member

    Thank you for quick reaction.

    But the feature is not accessible for me.

    See screenshot.

    Tested in 6.16 RC2 community edition.

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