distal-attribute
distal-attribute
distal-attribute
distal-attribute

Query profile is working for everyone?

somebi posted 4 years ago in General
My client freezes when i'm trying profile the query.

Can anyone confirm, that query profiling feature is working properly in the lastest version?

Thanks ;)

Btw why does ssh connection is establishing each time i'm trying to refresh the table list? O_o
It's damn annoying...
ansgar posted 4 years ago
Profile also freezes here. Obviously again I broke something due to query threads. Agrrr..

SSH and refreshing table lists don't have something to do with each other, have they?
ansgar posted 4 years ago
Fixed in r3781
somebi posted 4 years ago
It's ok mate.

About refresh yea. But why does client reconnects? Can't it keep connection alive? Maybe create some keep alive option?

Keep it going, i like HeidiSQL. ;)

Guess some unit testing suit is required as well. ;)
ansgar posted 4 years ago
Connections are automatically reconnected right before sending a query. No permanent keep-alive feature needed. Be honest, how often do you get this reconnect?

What problem makes you guess about unit testing?

somebi posted 4 years ago
Pretty often. The problem is, that reconnecting to ssh takes a while, about 3-7 seconds and it's pretty annoying if it's doing it every time.

About unit testing, it was just a suggestion for heidi development. :)
ansgar posted 4 years ago
You could increase your wait_timeout session variable in a autostart-script (see session manager "startup script"):

SET @@session.wait_timeout = 60*60*24;

somebi posted 4 years ago
Thanks mate. Now it's gone. ;)
somebi posted 4 years ago
Still disconnecting after inserting some dump in the query tab and launching refresh on tables list on the left.
It's only happening in this case.

I'm selecting option copy to clipboard dump option and paste it inside another heidi window. Then launching and doing refresh on tables list to see new inserted table.

Here is some log:
/* SQL Error (1548): Cannot load from mysql.proc. The table is probably corrupted */
SHOW TRIGGERS FROM `randevu_website`$$CREATE PROCEDURE myProc() DETERMINISTIC BEGIN DECLARE counter INT DEFAULT 0;
SHOW EVENTS FROM `randevu_website`$$CREATE PROCEDURE myProc() DETERMINISTIC BEGIN DECLARE counter INT DEFAULT 0;
# -------------------------------------------------------- # Host: 127.0.0.1 # Server version: 5.5.8 # Server OS: Linux # HeidiSQL version: 6.0.0.3784 # Date/time: 2011-04-22 18:39:01 # -------------------------------------------------------- /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET NAMES utf8 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; # Dumping database structure for randevu_website CREATE DATABASE IF NOT EXISTS `randevu_website` /*!40100 DEFAULT CHARACTER SET utf8 */; USE `randevu_website`; # Dumping structure for table randevu_website.departments CREATE TABLE IF NOT EXISTS `departments` ( `department_id` int(4) NOT NULL AUTO_INCREMENT, `controller` varchar(255) NOT NULL DEFAULT 'ads', `action` varchar(255) NOT NULL DEFAULT 'view', `single` int(1) DEFAULT NULL, `name_lv` varchar(255) NOT NULL, `name_ru` varchar(255) NOT NULL, `link_lv` varchar(255) NOT NULL, `link_ru` varchar(255) NOT NULL, `title_lv` varchar(255) DEFAULT NULL, `title_ru` varchar(255) DEFAULT NULL, `description_lv` text, `description_ru` text, `keywords_lv` text, `keywords_ru` text, `h2_ru` varchar(255) DEFAULT NULL, `h2_lv` varchar(255) DEFAULT NULL, PRIMARY KEY (`department_id`), KEY `link` (`link_lv`), KEY `link_ru` (`link_ru`) ) ENGINE=MyISAM AUTO_INCREMENT=17 DEFAULT CHARSET=utf8; # Dumping data for table randevu_website.departments: 9 rows /*!40000 ALTER TABLE `departments` DISABLE KEYS */; INSERT IGNORE INTO `departments` (`department_id`, `controller`, `action`, `single`, `name_lv`, `name_ru`, `link_lv`, `link_ru`, `title_lv`, `title_ru`, `description_lv`, `description_ru`, `keywords_lv`, `keywords_ru`, `h2_ru`, `h2_lv`) VALUES (1, 'ads', 'view', NULL, 'Sieviet/* large SQL query (8,8 KB), snipped at 2 000 characters */
/* 0 rows affected, 0 rows found. Duration for 1 query: 0,000 sec. */
/* Closing plink.exe process #2696 ... */
/* Connection to 127.0.0.1 closed at 2011-04-22 18:39:17 */
/* Connecting to 127.0.0.1 via MySQL (SSH tunnel), username root, using password: No ... */
/* Attempt to create plink.exe process, waiting 10s for response ... */
/* Connected. Thread-ID: 1198 */
ansgar posted 4 years ago
What do you mean - the "Cannot load from mysql.proc. The table is probably corrupted" is a server message. You should go and run

REPAIR TABLE mysql.proc.

somebi posted 4 years ago
Didn't fixed it either :)
mysql_upgrade fixed it

Please login to leave a reply, or register at first.