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

Forum Replies Created

Viewing 15 posts - 2,836 through 2,850 (of 7,398 total)
  • Author
    Posts
  • in reply to: #26967
    peterlaursen
    Participant

    sorry .. I did not see your 'nested reply' above!

    in reply to: #26966
    peterlaursen
    Participant

    1) We need the output of “SELECT VERSION()” from both servers/connections. The DUMP tells that the crash occurs when he handle the result of this query.

    2) Also tell: can you 'Test Connecton' to both servers from Connection Manager?

    The version no. (like 5.0.45) we get as string, and we convert every part of it into integers. The crash came when tried to convert the 3rd (like '45') part. One possibility is that the 3rd part of the version string is empty or invalid. If MySQL was compiled on this server (not using binaries from MySQL) the person building may not have passed correct details to the compiler.

    But strange though that it happens only after you have been 'doing things'. And not reproducable for us.

    This old issue may be related: http://code.google.com/p/sqlyog/issues/detail?id=435

    We should not crash of course, but sync tools will never work if version is not exactly identified. We would have to exit with an error message.

    in reply to: #26998
    peterlaursen
    Participant

    This is already listed in our TODO, refer to:

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

    I cannot guarantee exactly when we will support this, but we have set resources aside for 'catching up' with such small and medium requests.

    in reply to: #26994
    peterlaursen
    Participant
    in reply to: #26993
    peterlaursen
    Participant

    One more idea!

    Do you have floating numerical types (float, double) and is it used for defining the PK?

    See: http://dev.mysql.com/doc/refman/5.0/en/pro…with-float.html

    The WHERE clause generated by SQLyog GUI may specify a empty set. (“WHERE pkcolumn = 33.8” will fail simply if the value is stored internally as 33.8000000000000000000000007). We cannot support operations on FLOAT-PKs in SQLyog GUI for that reason! And also not tables with FLOATING types that do not have a PK.

    (RESULT tab will use the PK-column(s) in the WHERE, provided that all PK-columns were specified in the SELECT. If they were not all, or if there is no PK, the WHERE will match all columns in the result with AND) .

    in reply to: #26992
    peterlaursen
    Participant

    One idea: are you sure that you are not updating a table in another database than the one you think you do.

    In 6.56 this is possible (if the UPDATE statement is valid with the other database, MySQL will execute). If your SELECT uses full syntax (`database`. `table`) the database where the statement is executed (the last one selected from GUI) may be another one than the database selected.

    7.0 RESULT tab will prevent you to update tables from other databases than the ones from where the SELECT was executed.

    Alos try an update and check the statement in HISTORY and check MESSAGES as well.

    in reply to: #26958
    peterlaursen
    Participant

    The error that 'mysql server has gone away' may or may not be an issue with SQLyog!

    Is it *consistently reproducable* that this specific sequence of operations raise that error?

    Could you tell the server versions and attach the my.ini/my.cnf file for the server(s).

    We will analyze this tomorrow. Program should not crash anyway! Hopefully the DUMP will give usable information.

    in reply to: #26990
    peterlaursen
    Participant

    Supporting multiple results in a tab in GRID mode will be difficult, I think. Simply because every result set requires its own GRID settings.

    In TEXT mode it may not be a very big problem.

    in reply to: #26987
    peterlaursen
    Participant

    SQLyog 7.01 with the fix for this was released a few minutes back!

    in reply to: #26985
    peterlaursen
    Participant

    We have reproduced this crash. I think we have the information we need to fix this now!

    in reply to: #26981
    peterlaursen
    Participant

    Please zip and atach that dump file. That will make debugging this easier! The file has no information about your data.

    in reply to: #26979
    peterlaursen
    Participant

    The 'scheduled backup powertool' of ENTERPRISE version has several options that the 'export' has not – including

    * option to use a timestamp for naming the file

    * option to split backup into a file per table

    * option to backup all databases/all user data

    * option to choosing a specific encoding for the backup file

    We currently have no plans to add this in COMMUNITY version.

    in reply to: #26977
    peterlaursen
    Participant

    “Find in Blob Viewer” is a long standing request, refer to: http://code.google.com/p/sqlyog/issues/detail?id=469

    Blob Viewer resizability was not planned to be included in 'first shot of resizability implementation'. I think it will also be the most complicated dialogue. Also other Blob Viewer issues should be solved in same shot. But let us discuss this next week.

    As I told recently we have now one full developer assigned with all those small and medium user requests that have been accumulated, and we will 'catch up' with those – but I cannot tell exactly how much time it will take.

    in reply to: #26975
    peterlaursen
    Participant

    We have started coding resizability for dialogues where it makes sense.

    'manage indexes' will be among the first, probably to be completed next week. You can expect it in next release.

    in reply to: #26973
    peterlaursen
    Participant

    OK …

    Actually I have myself a Linux system (OpenSuSE 11) running in VirtualBox in WinXP. The Linux has a complete LAMP stack too.

    The problem is that the 'guest' ip (and the Linux/'guest' domain name) is not registered anywhere in the 'host' OS. Also the Internet and your LAN/WLAN does not know about the 'guest' OS. But every Virtualisation Manager has some host and guest extensions (to share folders, to share CD drives, USB drives etc). In your case there must be host and guest extensions that allow for http (and https) access from host to guest.

    That phpMyAdmin connects is really not at all MySQL related I think. I am sure that you would be able to connect to any website on the 'guest' (phpMyAdmin is basically a website only!). I am correct that phpMyAdmin is installed on 'guest'?

    I have one 'workaround' that works for me. I use a dynamic DNS service (www.dyndns.dk). That gives me a private subdomain on dyndns.dk (myalias.dyndns.dk). So when I specify host as 'myalias.dyndns.dk' in SQLyog on 'host' it will connect to the running MySQL server on 'guest' provided that I specify the correct port. (I use 3306 on the 'guest' and 3307 on the 'host', so with host as 'myalias.dyndns.dk' I can connect to both actually – what also lets me copy data, sync etc.).

    I will ask those of our guys that have most experience with VMware to help here!

Viewing 15 posts - 2,836 through 2,850 (of 7,398 total)