[peterlaursen]

Please tell the MySQL verson and the OpenSSL version used to generate the keys.

 

This error (a 4-digit error starting with “2”) is a MySQL client/protocol error. There is a similar report here https://bugs.mysql.com/bug.php?id=64870.  Does this have something you can use?

 

 

As a workaround can you try to SSH-tunnel instead?  Note that for this you will keys in Putty-format. The ‘Puttygen’ utility can convert keys. 

[peterlaursen]

@Mitch . are you still facing this problem?

[peterlaursen]

Such ‘false positives’ have been seen from time to time with any AV tool I know about. It usually get fixed in a few days with new signatures from the AV vendor. They will get reports by customers or the installed AV software will communicate with their servers.

[peterlaursen]

Please elaborate your environment.  From first post I think you are on a Mac using Wine? And server details – SSL in particular? 

[peterlaursen]

Thanks for the information.

 

But it is not clear to me why you are posting this.  Do you face any problems are you just posting in order to inform other people?  If there is a previous and related discussion somewhere, please link to it. 

[peterlaursen]

The crashdump does not point to any specific place in code. Crashdumps from Wine often don’t. So it won’t help us to identify the problem.

[peterlaursen]

“Is there some way to have SQLyog sort of ‘automatically’ decrypt and encrypt data?”

 

Short answer is NO. SQLyog will display what is stored in the database (unles you SELECT AES_DECRYPT(..) etc., of course).  And there is further one more problem.  An encryption algorithm may result in a string containing the NULL-byte (X00) and such data would be identified as binary data. And you should use binary datatypes (VARBINARY not VARCHAR and not at all numerical types) for storage if you really want to do this.

 

We have discussed many years ago to implement such feature, but decided that it would not be a solid business case for us.

[peterlaursen]

The ‘admin’ password is stored in MONyog.ini (passwords for other MONyog users – if you have such – are stored elsewhere).

 

Just open MONyog.ini in an editor and blank the password so that the relevant line looks like 

Password=

.. now restart MONyog and you can login as ‘admin’ with an empty password. After that set a new password from the MONyog interface .. tools .. change password. The new password has effect after next MONyog restart.

[peterlaursen]

Sorry for the late reply, but such option is not available in SQLyog Data Sync tool. But why do you want to do this?

[peterlaursen]

We realize there are problems. On some distros (or probably desktop environments) it sometimes work. On others never. 32 bit sometimes works and 64 bit not.

 

hmmm .. we will check again. But I don’t guarantee that it can be fixed. 

[peterlaursen]

The BIT type in MySQL is a huge problem. 🙁

 

In particular people coming from an SQL Server backgorund experience a lot of problems (because they use a MySQL BIT as they would use a SQL Server BIT, not realizing that they are actually very different things. They only have the name in common). 

 

It is the very implementation in the server that results in “Binary 1 (shown as b’1′) results in “SOH character” (because that is what ‘binary 1’  is when it is not stored as a MySQL BIT) as well as this “but b’0′ disappears” (because this is the NULL-character/NULL byte when not stored in a MySQL BIT).

 

Do you know MySQL documentation pages:

https://dev.mysql.com/doc/refman/5.7/en/bit-type.html

https://dev.mysql.com/doc/refman/5.7/en/bit-field-literals.html

 

This almost 10 years old blog summarizes the problems very well: http://www.xaprb.com/blog/2006/04/11/bit-values-in-mysql/ (though some of the regular bugs listed here are fixed. But the complaints about the implementation are still valid). I also blogged myself http://blog.webyog.com/2011/12/04/a-little-bit-about-bit-again/ 4 years ago about another oddity with MySQL BIT.

 

It is much easier to use a TINYINT(1) rather than a BIT(1) to represent a boolean value in MySQL. But since MySQL supports it, we should also handle it. We will check this case.

 

The last MySQL docs page lists a workaround: “To display them in printable form, add 0 ..”. You may use this (ie execute “SELECT non_bit_type, bit_type+0 FROM table;”) and export from RESULT tab.

[peterlaursen]

I think we should continue in private here.

 

Please send a mail to [email protected] wiith screenshots of how you have filled the “MySQL” and “HTTP” tabs in SQLyog Connection Manager.  Please refer this Forums post in the mail as well. 

[peterlaursen]

I suspect some browser plugin being the culprit here.

 

Do you have an option to try from another system, for instance? 

[peterlaursen]

As first step, I would suggest that you try to clear the browser cache. 

[peterlaursen]

I think the problem is another: It looks like the database context/default database is not restored after a reconnect. 

 

 

Please try:

SET wait_timeout = 5;



-- now be idle for more than 5 seconds so that the server will time out the connection

SELECT functionname(); -- you will get the error, I think? Maybe only sometimes?



-- again be idle for more than 5 seconds

SELECT databasename.functionname(); -- now you will *not* get the error, I think?



-- again be idle for more than 5 seconds

USE databasename;

SELECT functionname(); -- now you will *not* get the error, I think? 

 

Am I right? It even happens randomly for me like this (also when selecting from a table). Not sure yet if the issue is in SQLyog, the API or the server. 

[Author]

Posts