Forum Replies Created
-
AuthorPosts
-
peterlaursen
Participant@Navya .. he told that this flickering is a multimonitor issue!
Did you check with a multimonitor setup?
peterlaursen
ParticipantNavya .. I think you did not get the problem here!
The user wants to work in the RESULT tab and after a while execute the same query again! You can execute using F9 even if editor does not have focus (it has 'memory' of its last postion in the editor). But F8 does not work like that. That is inconsistent.
peterlaursen
Participantyou have to specify the exact meaning *a lot of times*. Is it happening completely randonly? Can you connect to the tunneller from a browser when this happens?
If so I think there is very little you can do. Except for telling/complaining to the Sysadmin that you have frequent problems connecting to a specific PHP page (it does not matter which one, really!) or find better hosting. It may be because the webserver system is overloaded (too 'tiny' hardware or configuration settings as compared to the load/traffic on the server).
Do you have the possibility to use SSH tunnelling?
You could try SQLyog 6.54 too. Your free upgrades have probably expired, but the 6.54 TRIAL will run for a month if you never had a 6.x TRIAL installed before.
peterlaursen
Participantthanks for this hint!
We will study this!
peterlaursen
Participant“I've recently upgraded from 6.51 where there was no such thing.”
.. so this is probably a 'side effect' of the fix in 6.52, I think. We will discuss this!
peterlaursen
ParticipantWe fixed some related issue recently (in 6.52 I think). What is your current version?
This is not reproducable here. Can you tell the video hardware and driver version (from device manager) ?
peterlaursen
Participantconfirmed as described .. and there is one more strange behaviour actually!
1) write in editor: select * from mytable;
2) press F9: result tab opens wit dropdown in 'read-only' state
3) press F8: result tab opens with dropdown displaying 'mytable'
4) now press F9 again: result tab opens with dropdown displaying 'mytable' (not in 'read-only' state)
I think the code behind F8 goes back to version 4.0 and was not properly changed to reflect changes in GUI design since then!
We will check those details next week!
peterlaursen
Participant“Save Query Builder Layout” is something we have discussed only briefly. Not decided when we will do this. We can save as “Schema Designer Layout”, but a “Query Builder Layout”” poses more problems (basically storring GRID information). Alternatively we could provide and option to 'reverse engineer SQL query into Query Builder' .. but hat is an even bigger task. Bascially priorities depend on the demand!
The query itself can be stored, of course (as a file and a 'favorite', but I think you know).
peterlaursen
ParticipantI have one more request:
If you use SQLyog 'duplicate table' and only duplicate the STRUCTURES of the tables, will the 'duplicates' (with no data in them) then sync faster?
peterlaursen
ParticipantI am sorry, but I was too optimistic.
We use SHOW TABLE STATUES also to retrieve ENGINE, CHARSET, COLLATION, TABLE-level comments (and possibly more). And as Struct Sync shall work across different MySQL version it is complicated actually.
Due to labor day tomorrow and the weekend we can only return to this discussion on Monday.
peterlaursen
Participantbtw: you really have some server parameters here:
query_cache_size=99M
tmp_table_size=101M
innodb_buffer_pool_size=569M
as regards:
myisam_max_sort_file_size=100G
myisam_max_extra_sort_file_size=100G
see this:
http://bugs.mysql.com/bug.php?id=10163
http://bugs.mysql.com/bug.php?id=339
and
http://dev.mysql.com/doc/refman/5.0/en/ser…_sort_file_size
myisam_max_sort_file_size: “The maximum size of the temporary file that MySQL is allowed to use while re-creating a MyISAM index (during REPAIR TABLE, ALTER TABLE, or LOAD DATA INFILE). If the file size would be larger than this value, the index is created using the key cache instead, which is slower. The value is given in bytes.”
peterlaursen
ParticipantI think we can provide a test build in less than 2-3 hours where the query has been replaced!
I will give some more background on this. When SQLyog 5.0 was released we originally used SELECT FROM I_S, but changed to SHOW TABLE STATUS for 2 reasons.
1) the above-mentioned bug in early MySQL 5.0
2) frequently when MySQL5.0 was installed on top of a previous version the “SELECT … FROM I_S …” query returned nothing! This was due to incorrect upgrade procedures or privileges settings on the server, but at that time it affected lots of user that were customers at ISP's where this was the case! We have been reluctant to return to “SELECT … FROM I_S …”, because we can then expect reports here that “SQLyog finds no table in my database”… 🙁
Anyway we will create a test build where “SELECT … FROM I_S …” is used and let us see the difference on your system!
peterlaursen
ParticipantOk .. I found something!
http://mysqldatabaseadministration.blogspo…records-go.html
Quote:InnoDB doesn't keep a row count in the table itself, as MyISAM does. This is because of transactional concurrency requirements. Therefore, count(*) works differently; in MyISAM, it can just ask the table how many rows it has, but in InnoDB, it has to scan some index and find out. This is slow. For that reason, the SHOW TABLE STATUS value is only an estimate, and can be very wrong, in InnoDB.From the attached configuration file I think that you are using InnoDB extensively (you have rather large InnoDB buffer settings etc)?
I think we did not realize or consider that SHOW TABLE STATUS will need to COUNT before returning result!
peterlaursen
ParticipantIt still would be very usefull if you can provide a structure only dump – at least for a single table where SHOW TABLE STATUS … is slow
peterlaursen
ParticipantCode:show table status from `db1` where engine is NULL
show table status from `db2` where engine is NULLboth these queries take approx 20 secs
I actually observed myself yesterday that this query can be very slow (up to one second here with the examples I have available)
Actually we have another option, that is “SELECT …. FROM INFORMATION_SCHEMA.TABLES WHERE .. “. We have de-selected this till now because of bugs in MySQL I_S implementation in the early 5.0 tree. But maybe we should consider it again (probably nobody uses those early 5.0 alpha/beta servers any more!).
With versions up to 4.1 we simple SHOW TABLES .. but on 5.0+ this does not distinguish between TABLES and VIEWS. So not usable for structure sync with recent server versions.
We will check with your dump and if it is reproducable that this statement takes so much time wiht a specific SCHEMA, I think I will also report it to http://bugs.mysql.com. And of course replace the query ASAP if that is the problem here!
-
AuthorPosts