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

Forum Replies Created

Viewing 15 posts - 3,361 through 3,375 (of 7,398 total)
  • Author
    Posts
  • in reply to: #25647
    peterlaursen
    Participant

    I think we did not 'catch' that this was an issue with NT4.

    SQLyog 6.x will only work on Win2000 and later (+Wine) because it depends on the unicode implementation (utf16) that was started with Windows 2000 and on some 'primitive' routines in the OS itself used to convert between ANSI, UTF8 and UTF16.

    SQLyog uses UTF8 internally as it is the unicode charset that works best for a MySQL client. Whenever SQLyog communicates with Windows it (has to) use(s) utf16.

    Actually when you upgraded from 5.x to 6.x the sqlyog.ini file got re-encoded from ansi to utf8. That is probably why it cannot be read now.

    Please try.

    1) Open sqlyog.ini in Notepad .. save as .. select ANSI

    2) Delete or rename sqlyog.ini (note that your connections details will be lost)

    in reply to: #25651
    peterlaursen
    Participant

    Actually we plan to detect unicode (uft8 and ucs2/utf16) automatically. I do not think a user specification is required with those. But an option for user to specify charset would be useful with 'problematic' non-unicode charsets (like ujis, big5 etc.)

    in reply to: #25644
    peterlaursen
    Participant

    I don't have no idea about the exact reason, but I agree it must be SSH-related.

    I also think version 6.2 to solve this. From this version the complete connections chain

    SQLyog <> Plink <> SSH daemon <> MySQL

    will be reconnected when SQLyog reconnects. Currently we reconnect from SQLyog to Plink only. SQLyog will reconnect when server is not reachable, but if problem is not between SQLyog and Plink it won't help (and it is likely somewhere else!).

    First 6.2 beta is probably 10-14 days away.

    in reply to: #25640
    peterlaursen
    Participant

    I am sorry if I did not express myself clear enough.

    Currently the graphs display 'as is' (plotting latest sampled values) only and cannot be changed. Both options will be added in version 2.0.

    in reply to: #25637
    peterlaursen
    Participant

    1) Please tell: What does 'using a third-party connection manager' mean? How this in relation to SQLyog? I do not understand the meaning of this!

    2) Please reproduce this again. When the situation has occured click the SQLyog HISTORY tab. Copy the content of the tab to the editor and execute statements one by one. We need to find out what (sequence of) SQL-statements triggers this. No matter if you use the Object Browser or not, SQLyog will only communicate with the Server by sending SQL and the error message is a server error message. It is a specific sequence of SQL that gives this result and nothing else!

    3) After connection please execute “SHOW GRANTS;” and paste result here.

    4) Do you have an option to try another server ?

    5) Do you know if the server was intalled 'on top of' an earlier version. If so were all upgrade scripts executed properly after installation?

    in reply to: #25638
    peterlaursen
    Participant

    There are no plans to change graphs of the 'dashboard' interface in near future.

    However in next release we will add 'microscopic' as well as 'macroscopic' analysis options in the 'show all' interface:

    What we have almost finished implementing at the moment is (using examples):

    * 'microscopic' option example: If TIMEFRAME is 1 hour and sample interval is 2 minutes it will tell you details for every (latest) 30 samples in the TIMEFRAME

    *'macroscopic' option example: You will we able to generate graphs of aggregated data (using all 'historical' data stored in MONyog embedded database) for a certain interval grouped by a time interval (hour/day/week etc). User will be able to specify what aggregate function to use (like SUM/AVERAGE/MIN/MAX).

    in reply to: #25635
    peterlaursen
    Participant

    sorry for 'spamming' this psot where Mahesh had allready replied!

    However the server information might be important too!

    in reply to: #25634
    peterlaursen
    Participant

    1) To get an idea of what triggers this error message please copy the latest SQL sent to the server from the HISTORY tab. Paste it here and try manually executing

    2) Tell:

    *What is the server platform?

    *What is exact server version?

    *What is the setting for 'lower_case_table_names' variable?

    3) Also please try 6.15 RC2!

    in reply to: #25618
    peterlaursen
    Participant

    a. “Columns” folder into the Tables items of the database tree. What are they used for ? there is no visualization when I click them, in none of the panels. Are they useful to something ? some data display about their nature, properties, foreign keys constraints etc. should be useful. Otherwise eliminate them, because useless and misleading.

    >> You can expand the Object Browser to tell you the name of existing columns. Use it or don't use it .. your choice!

    b. a separate window for the data display and manipulation with advanced tools should be required.

    >> I do not understand.

    c. a context sensitive help should be introduced, especially for what the commands and the buttons is about.

    >> Agreed that this could be better. is there but not very extensive. This is being constantly improved with tooltips, 'what is' buttons etc. But let me remind you that a lot of professional MySQL users use the command line client extensively …

    in reply to: #25617
    peterlaursen
    Participant

    Also this

    “a. Every time I open an ALTER TABEL window I must resize the columns, especially the columnames column.

    b. Every time I change table, in the TABLEDATA view I must resize the columns, aso if I got back and foth from two tables, from a table to another to the other and back again

    Nowhere the screen tables columns are saved. Columns widths should be saved always, instead.”

    .. has been discussed before. Basically a client like SQLyog does not store any data. And the server has not such data either. We could in theory store such settings locally (similar to what we do with autocomplete), and if you use SQLyog with a few databases only it is no problem. However if you have hundreds of very big databases it will take a lot of disk space. And if another client ALTERs the database the locally stored data will be invalid.

    But basically I think that you with this request do not fully realize the client-server nature of MySQL/SQLyog usage! Typically there will be many clients for every database and every server.

    in reply to: #25616
    peterlaursen
    Participant

    a. there is not security data feature to prevent any fortuitous or unintentional modification of database data.

    >> There should not be either, I believe. Such security features should be in the server not the client. Use server User management appropriately

    b. there is no differentiation in windows when I open different databases with the same name on different servers or tables with the same name on different servers (production, test and development for instance).

    >> You should define a connection name in the connection manager for every connection!

    c. Database names are too small and they are not clearly rendered visibles in the upper part of the window. One should be capable to distinguish one database to the other with a simple perception, not with a visual search of a small detail in the upper part of the window.

    >> Don't understand 'not clearly rendered visible'. Please explain! Screenshot?? But the compact design is a intentional design. But you may change fonts in 'preferences'

    in reply to: #25611
    peterlaursen
    Participant

    1) The cursor behaviour as described is a minor bug! No reason why the cursor should jump!

    2) The 'execute' function is disabled, and only 'execute all' is enabled in those special tabs where templates for SP's etc. open (CREATE/ALTER). This has been discussed a lot and we may change it – there are PRO's and CONs.

    But the basic consideration is that ALL statements on that tab will have to be executed to make CREATE/ALTER … statement functional.

    in reply to: #25615
    peterlaursen
    Participant

    I will reply to some of your comments later.

    However, SQLyog is NOT a Delphi program. It is a C++ program! Just for clarity!

    in reply to: #25608
    peterlaursen
    Participant

    I replied in you ticket!

    in reply to: #25599
    peterlaursen
    Participant

    No – not possible at the moment.

    What we do plan is to add more 'conflict rules' so that the program can decide what to do with rows with identical PK but different data. A rule like 'most recent takes precedense' is one of those new rules. Currently only 'source overwrites target' rule is possible.

Viewing 15 posts - 3,361 through 3,375 (of 7,398 total)