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.
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.
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.
“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.
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.