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

Forum Replies Created

Viewing 15 posts - 301 through 315 (of 7,398 total)
  • Author
    Posts
  • in reply to: #34798
    peterlaursen
    Participant

    It should not change when upgrading. Anyway: go to menu .. tools .. preferences .. ‘Font & editor settings’ -tab and note the ‘Case’ groupbox.  Here you have two combo’s/dropdowns for ‘keywords’ and ‘functions’ lettercase setting.

     

    (Besides: this is unrelated to ‘autocomplete’.  It works also if autocomplete is completely turned OFF (in the ‘powertools’ tab for preferences settings), This is purely and solely a formatting option in the editor recognizing keywords and names of built-in functions.

    in reply to: #34787
    peterlaursen
    Participant

    We have no clue. THis error was never reported before. The system (some native WIndows .dll for instance) must have been damaged somehow . The resizing of SQlyog is a basic Windows API (http://en.wikipedia.org/wiki/Windows_API) functionality and not our code. When programming we just instantiate awindow using a standard Windows API function (it could be this one http://msdn.microsoft.com/en-us/library/windows/desktop/ms632680(v=vs.85).aspx – but not sure about this). We have not changed anything in this respect.  because there is basically only one way to do it in Windows.

     

    One reason for the failure could be a hardware failure (disk, disk controlller, RAM blocks etc.) resulting in corruption in one of the .dll files hosting the Windows API functions. But that is only one possibility, of course – it remains guesswork. But hardware issues are not uncommon with new hardware.  Last time I saw some statistics, it was around 15% of systems shipped that shipped with a hardware defect or developed one during the first weeks or months of use.

     

     

    Since it is working now, I think you should first create a manual ‘system restore point’ and next apply all updates available from WIndows Update to the system. And next updates to what applications you have running (such as AV etc.). If you don’t face any issues after that the conclusion must be that you’ve faced some system corruption for any reason.

    in reply to: #34782
    peterlaursen
    Participant

    Is this sentence complete: “Ever since I put the new update onto my computer, every time I try to resize the panes in sqlyog.”? I don’t think so. “It freezes”, I understand. But only the application or the complete sysstem? Are you able to launch the Task Manager with CTRL+ALT+DEL?

     

    I have the same system (Windows 7 Home Premium 64bit) and it does not happen here with any version.

     

    Please try to 

    1) temporarily disable what AV/security software you have.

    2) reboot system and launch ONLY SQLyog and also run as few background processes as possible.

    3) Check the system logs (control panel .. administation .. logs .. and probably the “ACEEventLog group) if some information is available.

     

    We need to locate what happens on your environment specifically. It may be some interaction by another process.

    in reply to: #34772
    peterlaursen
    Participant

    Did you read thiis documentation paragraph https://static.webyog.com/docs/MONyog/MONyog_MySQL_Monitor_Database_Schema_Introduction.htm?

     

    We also have an old blog here http://blog.webyog.com/2009/07/29/monyog-database-schema-explained/  – it is a little more elaborate/verbose about the principles, but all details are not up-to-date today.

     

    For every server registered you will find a .mysql.data SQLite file (and possibly more depending on what functionalities you have enabled in MONyog – systems monitoring, query sniffer etc.).  Most of the databases follow the same design idea described in the blog. The culprit is this passage (search/scroll down).

     

     

    1) Everytime MONyog sends a statement like SHOW VARIABLES/STATUS of some kind (or fetching a OS metric from Linux /proc folder) one row is INSERTED into [timestamp_master] table with information about current time and the metrics retrieved for each such statement will be INSERTED into [snapshot_master]. The [snapshot_master] table contains the metrics details. The [timestamp_id] column identifies when metric details were like that. And also note that timestamps in MONyog databases are unix_timestamps.

    2) And actually we do not always INSERT into [snapshot_master]. Only if the particular metric was changed since last time something was INSERTED for that metric we will INSERT again… 

     

     

    This is actually some kind of ‘key-value store’ (where the timestamp of a metric is the key) similar to what you would find in most ‘NoSQL databases’ – but implemented in SQL/SQLite in case of MONyog.

    in reply to: #34769
    peterlaursen
    Participant

    In the ‘tools’ menu there is also an option to ‘Export/Import Connection details’.

    in reply to: #34756
    peterlaursen
    Participant

    If user does not have privilege to read table content I don’t see how this could be possible. Table comments are stored in the table itself.

     

    But I am not sure I understand!

    in reply to: #34754
    peterlaursen
    Participant

    I am sorry, but I do not understand this question/request. Please elaborate. 

    in reply to: #34758
    peterlaursen
    Participant

    + check trivial firewall issues.  it is not certain that your firewall lets SQLyog connect even if it does allow a browser to do so.

    in reply to: #34740
    peterlaursen
    Participant

    I am terrible sorry, but our conclusion is that original files cannot be recovered from a .zip suffering from this.  We have tried everything and also contacted the author of the .zip library and there is no way, he tells. 

    in reply to: #34739
    peterlaursen
    Participant

    Unfortunately we have also not yet found a solution.

    in reply to: #34744
    peterlaursen
    Participant

    🙂

    in reply to: #34742
    peterlaursen
    Participant

    @jduplechain

    Pleas do not use the option to 'report'. 'report' is something you do to a Forums 'moderator' in order to report breakage of ethical rules (reporting spam, offensive language etc.)

    We have seen this post and we will conisder it after the weekend.

    in reply to: #34737
    peterlaursen
    Participant

    We are trying to find a solution. We will do our best to find some method to retore (fully or partially) what is possible. But I cannot guarantee anything and it will only be after the weekend as we cannot find the time today.

    I fully understand that you may be situated in a precarious situation (if you are not able to generate another dump) trusting SQLyog. But basically you should always verify that backups will restore before relying on them – and that applies to any kind of backup generated by any tool.

    in reply to: #34735
    peterlaursen
    Participant

    This tool claims to be able to fix .zip's with a checksum error:

    http://www.essentialdatatools.com/products/objectfixzip/

    (a google search “fix bad zip archive” finds more).

    in reply to: 2-Way Sync Behavior With Sja #34096
    peterlaursen
    Participant

    You can do a two-way sync. But it works like this: first a one-way sync in one direction (source>target) and next a one-way sync in the other direction. If you insert data in both between sync jobs you will have do define the Primary Key in such a way that the same PK-value is not created on both.

    There are dozens of similar replies explaining (and also more elaborate) the importance of understanding how Data Sync works with the Primary Keys of tables..

Viewing 15 posts - 301 through 315 (of 7,398 total)