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

Forum Replies Created

Viewing 15 posts - 3,046 through 3,060 (of 7,398 total)
  • Author
    Posts
  • in reply to: #26266
    peterlaursen
    Participant

    Please search a little before posting! This has been asked an replied LOTS of times!

    a FAQ:

    http://webyog.com/faq/content/8/99/en/does…l-keywords.html

    another Forums post:

    http://www.webyog.com/forums//index.php?showtopic=3774

    (no need to repeat!)

    in reply to: #26263
    peterlaursen
    Participant

    You are right that we do not maintain a single LONG HTTP session. We establish a new session for every query.

    If you can find more details we will look into it.

    I remember a few similar situations where a user had this problem from one specific location (like his home) but not from other locations (like job, friends).

    So this is why I wrote that is could be an issue with the LINE – and not necessarily the ISP.

    The problem is that SJA does not really *know* WHY it stops, it only *records* it. So we cannot tell what we should repeat. Addtitionally SJA does not attempt to reconnect (unlike the GUI).

    in reply to: #26265
    peterlaursen
    Participant

    Currently we will always use an uncommpressed XML stream as defined in HTTP protocol.

    What is the compression option you are thinking of? gzip/vizp/zlib with PHP? I think that is the option there is?

    Such compressed protocols are not always good – actually nowadays the are of sometimes bad beause it moves the load from the connection to the server and client machine instead . With the speed of TCP connections of today they are often irrelevant. This is also the situation with the MySQL compressed protocol.

    Anyway let us discuss if some compression is possible and could be an idea with batch jobs (with the GUI it is definitely irrelevant).

    in reply to: #26261
    peterlaursen
    Participant

    This is simply (I guess) an issue with the stability of the HTTP conenction.

    I think the error does not occure exactly the same place every time?

    It may be a godaddy issue (some timeout setting) or it may be an issue with you Telecom company or you DNS provider. Defect cable, switch etc. somewhere for instance.

    Do you have an option to try from another location?

    in reply to: #26259
    peterlaursen
    Participant

    We will have to research and debug it.

    If it is a Wine issue we should report it.

    But maybe there also is a workaround.

    in reply to: #26256
    peterlaursen
    Participant

    Also try restart server without the 'bind-address'.

    I am wondering if this new connection (that is piped through wineserver) is not recognized as a connection from 127.0.0.1.

    Have you upgraded Wine lately?

    in reply to: #26255
    peterlaursen
    Participant

    hmmm … now it is strange.

    What do the statements

    * show variables like 'max_connections';

    * show variables like 'wait_timeout';

    return?

    How many connection threads are there?

    Are you connection as 'root' (or another user that has SUPER privilege)?

    Was it possible that you could try restart MySQL? Does error persist after this?

    I am afraid that further analysis of this will have to wait till tomorrow.

    in reply to: #26253
    peterlaursen
    Participant

    Maybe the max no. on connections has been reached?

    That is why I asked you to try open one more SQLyog instance!

    You should know that when max no. of connections has been reached it is still possible to connect ONCE as root.

    Try in SQLyog to tools … show … processlist.

    There may be lots of processes running from connections that were not closed properly! Try killing a few!

    in reply to: #26250
    peterlaursen
    Participant

    Please stop here. It is not possible to discuss in two threads at the same time. We continue in the other one.

    One discussion per problem please! (and it is basic netiquette too!)

    in reply to: #26238
    peterlaursen
    Participant

    I saw that image of course.

    It clearly tells that you have selected 'all time/current' timeframe.

    Could you try comparing table values and the graph in the 'Delta' timeframe?

    'Delta' timeframe diplays most recent values. (more info in documentation).

    When you are referring to 'Dashboard' it seems not to be what we (and the program documentation) call the Dashboard. Clear terms make discussion easier! I think you are referring to the graphics popup? The Graphics popup seems to have values very different from what the AJAX grid reports. Like that? If you only in 'Delta' timeframe you should expect them to be comparable. The documention explains furhter.

    If you want us to reply to your questions you will have to reply to OUR questions (even if you think those questions are silly and even if you think we should know!) because before we can reply we will have to understand the question. It won't help that you are telling that you have told.

    in reply to: #26251
    peterlaursen
    Participant

    “The error message changed by the way. It SAYS Error no. 2003 Can't connect to..”

    Well then our the fix worked! A proper error message is displayed. But this won't help you of course.

    You should note that is it not an AUTHENTICATION error, but a CONNECTION error.

    An export is executed in a new connection thread. There may be some setting on the network or in MySQL configuration that prevents this new connection (such as a max connections per user setting). Can you have two SQLyogs connected at the same time with same user?

    If you have bind-address 127.0.0.1 then you should only be able to connect from localhost. As it is COMMUNITY you are using you are not tunnelling.

    Is server and SQLyog on the same computer? (If not I do not understand how you can connect at all!).

    If you are in control of server configuration please try to comment out that bind-address 127.0.0.1 and restart server.

    You probably read this allready?

    http://webyog.com/faq/content/23/15/en/err…_t-connect.html

    in reply to: #26247
    peterlaursen
    Participant

    Fix is not in 6.16 (latest stable) – only in the 6.5 tree. Please try 6.5 RC.

    in reply to: #26245
    peterlaursen
    Participant

    Those are known issues.

    Please refer to:

    http://code.google.com/p/sqlyog/issues/detail?id=12

    Actually I was about to ask you if you experienced this! But now no need I guess.

    Maybe we should consider providing 'alternative shortcuts'. It seems that ENTER and SPACE behaves different that keys on Wine/Linux.

    in reply to: #26242
    peterlaursen
    Participant

    I create the table

    CREATE TABLE `table` (

    `id` int(11) default NULL,

    `bla` int(11) default NULL,

    `pli` int(11) default NULL,

    `wlu` int(11) default NULL

    ) ENGINE=InnoDB DEFAULT CHARSET=utf8

    see attached images

    1) columns display after writing table alias followed by “.”

    2) when there is only one match left a tooltip pops up

    3) ctrl+ENTER displays *everything* with first possible match highlighted

    4) ctrl+SPACE displays possible matches

    5) (no image) Typing “select * from `table` mytab where my” and pressing TAB repeatedly will display “MyISAM”, “mysql”, “mytab” and all over again from the beginning as they are the 3 possible function/keyword/identifier/alias matches. before 6.5 “mytab” would not come.

    [attachment=867:auto.jpg]

    [attachment=868:tooltip.jpg]

    [attachment=869:ctrl_enter.jpg]

    [attachment=870:ctrl_space.jpg]

    Have you created a table named `table`? Do you have Autocomplete enabled in 'preferences' at all? Do you use the Enterprise version?

    in reply to: Character Set Doesn't Work With Umlaut (Ü,ö,ä) #24504
    peterlaursen
    Participant

    1)

    OK .. I should make it clear in the FAQ that batch jobs will have to SET NAMES themselves according to the encoding of data. Currently only the GUI thread is described in the FAQ.

    2)

    Let us take an example:

    I have the characters here 'æøåÆØÅ' (Danish characters – non-ASCII, MySQL 'latin1' characters and ANSI/western code page characters).

    in ANSI they are encoded “E6F8 E5C6 D8C5”

    In UTF8 they are encoded “FFFE E600 E500 C600 D800 C500”

    (in ANSI such accented characters are 1 byte each – in utf8 they are 2 byte)

    … but the point is that “FFFE E600 E500 C600 D800 C500” is also a valid ANSI string that prints like “æøåÆØÅ” (a 12 character string) with western codepage settings. Neither SQLyog nor the MySQL server has a monkeyman's chance to know if you want to import the byte pattern “FFFE E600 E500 C600 D800 C500” as the string “øøåÆØÅ” or as “æøåÆØÅ” unless you tell – basically because they both are valid and only you can tell that. That is what they SET NAMES statement (or SET character_set_client, SET character_set connection etc.) is for!

    So I simply do not think we can detect that.

    We do detect the file encoding however, so we can read ANSI files containing utf8 byte sequences (and byte sequences in any charset supported by MySQL actually – and even more weird we can import utf8 data stored in a utf16 file!). Actually in SQLyog before 6.0 if you exported a uft8 table you would see “øøåÆØÅ” appearing as “æøåÆØÅ” because with the old versions before 6.0 we did not use utf8 encoding (or another unicode encoding) for the file itself – but we did (or more correct: the server did!) for the byte/octet stream of the data in the file. So it would import correctly, but display garbled in an editor.

    But if you export with SQLyog the correct SET NAMES statement will be on top of the file.

Viewing 15 posts - 3,046 through 3,060 (of 7,398 total)