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

Forum Replies Created

Viewing 15 posts - 3,031 through 3,045 (of 7,398 total)
  • Author
    Posts
  • in reply to: #26296
    peterlaursen
    Participant

    bug confirmed!

    in reply to: #26298
    peterlaursen
    Participant

    You are right. This we should support. This is a known issue that GUI does not support it.

    in reply to: #25545
    peterlaursen
    Participant

    Since we started using UTF8 internally in 6.0 we have a problem.

    The problem is that currently we have no way to retrieve in length of a string in CHARCTERS, only as BYTES from the Scintilla editor used for text display. Our own GRID code can handle it however. As a consequence the strings

    ABCabcn

    Àbcàbcn

    ÆØÅæøån

    ABCabcñ

    .. etc. do not align properly in text mode as UTF8 characters can be 1, 2, 3 bytes long

    This already affects OBJECTS tab, RESULT tab in text mode ext. This I think we can live with – though I also think we should now focus on it. But in DATA tab we cannot live with it. So this will have to be solved first.

    in reply to: #26286
    peterlaursen
    Participant

    I have added this request to our issue tracker for MONyog.

    I think it is a good point that the graphs should *somehow* indicate the 'yellow' and 'red' alert levels. There may be other ways to do this and we will consider.

    in reply to: #26291
    peterlaursen
    Participant

    Not reproducable for me with 4.1.22 as source and 5.0.51a as target with SQLyog 6.51. See attached.

    [attachment=881:identical.jpg]

    Did you tell your SQLyog version? If an upgrade won't help, I think it must be a collation bug with your MySQL 4.1.

    Please first try upgrade SQLyog, if problems persist let us see the returns of

    Code:
    SHOW FULL FIELDS FROM `t`;

    from both tables/databases/servers.

    in reply to: #26289
    peterlaursen
    Participant

    Support for charsets&collations were added in version 6.1.

    If you want to try with 6.07 and your tables, you can create a ticket and I will give a link to 6.07 Enterprise.

    in reply to: #26288
    peterlaursen
    Participant

    There is no MySQL 4.11! Do you mean 4.0.11, 4.1.11 or 4.1.1 or … ?

    I think I can figure out that is is 4.0.11. Collation specifications do not apply to 4.0.x (it was introduced in 4.1.x only). Column level comments are not supported in 4.0x either. I think you have 5.1.x asand 4.0.11 as ? Please confirm or correct!

    Also please attach the returns of “SHOW CREATE TABLE” for bothand

    But anyway .. Structure sync is supposed to work across MySQL versions, so likely this is a bug introduced when we introduced support for collations in structure sync. I will try to verify that when you have provided requested details.

    It my assumption is correct you will have to copy the sync script to an editor and

    1) remove column level comments

    2) remove COLLATE

    .. so that it becomes “alter table `database_name`.`t` change `id` `id` int(11);” with that example.

    and … hmmm … this

    Code:
    COLLATE NULL NULL first, COMMENT=''

    .. looks strange! very strange 🙁

    in reply to: #26287
    peterlaursen
    Participant

    SQLyog does not use ODBC to connect to MySQL. The client library and 'connector' is the MySQL C-API – the most efficient way to connect to MySQL.

    For secure/encrypted connection we support SSL (native with the MySQL API), SHH-tunnel and HTTPS-tunnel (ENTERPRISE version only).

    SQLyog cannot act as a 'generic proxy' for other applications. I think that was your question?

    in reply to: #26279
    peterlaursen
    Participant

    An addition: BULK inserts are used when you are syncing to an empty target only.

    For speed optimization refer to:

    http://webyog.com/faq/content/11/61/en/how…highlight=speed

    in reply to: #26274
    peterlaursen
    Participant

    I am not sure either if this is a SQLyog issue, or you are asking for advice only!

    Are you saving using SQLyog or the interface of this game?

    in reply to: #26240
    peterlaursen
    Participant

    I will reply to this

    “For the All Time/Current view, if the current full table scan shows 17% why doesn't the graph also show this? Why do you indicate there is not a correlation between the value currently shown on the page and the generated report?”

    The reason is that the server status variables may have recorded situation from *LONG TIME* before MONyog was installed. The graphics popup displays 15 most recent 'captures'. The 'All Time/Current' table view may be an average of serveral months on even years situation on the server.

    So it is not obvios that your image shows something wrong.

    This

    “For the Delta view, I haven't been lucky enough to view it when the % is lower than 95%. The generated report certainly shows very high numbers which matches the number displayed on the Delta page.”

    … also indicates to me that *recently* you have hade very high full table scan rates. Likely that at *some point of time* an application was installed that uses indexes inefficiently. I think the longer time the server will run without restart or FLUSH STATUS the more will metrics in 'All Time/Current' increase.

    If you are not sensitive about the server status variables you can issue “FLUSH STATUS” from a client (like SQLyog) and all possble *old situations* recorded in status variables will be reset.

    in reply to: #26270
    peterlaursen
    Participant

    bug confirmed! will fix tomorow!

    in reply to: #26268
    peterlaursen
    Participant

    ok .. that is the 'backdraw' of the current implementation. Whenever you a saving (no matter if data were entered by user or retrieved from the database) a string that is a valid keyword will be treated as a keyword.

    Anyway – just turn off the 'smart keywords handling' in preferences when working with this table.

    in reply to: Error No.: 0, While Creating Sql-dump #24592
    peterlaursen
    Participant

    Actually we found one more bug.

    Please refer to:

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

    If you do not mind, we would appreciate if you would try 6.5 RC2.

    in reply to: #26260
    peterlaursen
    Participant

    Actually we found one more bug.

    Please refer to:

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

    If you do not mind, we would appreciate if you would try to upgrade Wine again and try 6.5 RC2.

Viewing 15 posts - 3,031 through 3,045 (of 7,398 total)