[Ritesh]

We have not changed anything in that area.

Quote:

However, this new upgrade seems to have removed the add credentials option from the Tunneling Connection configuration.

Do you mean that the option is disabled in the connection dialog or its not working?

Is it possible to give us temporary access to your server with the same settings for couple of days?

[Ritesh]

Does it disappear after showing you the connection dialog or before that?

By fresh installation do you mean that installed SQLyog Enterprise 5.11 on a new folder or SQLyog.ini was present in the folder?

[Ritesh]

I have asked my developer to work on it. If its a bug, will be fixed in the next release of SQLyog.

[Ritesh]

Added for v5.2.

[Ritesh]

Added in the TO-DO list.

[Ritesh]

Nice suggestion. Let me think about it and we can start a discussion thread on how to improve the Autocomplete feature.

[Ritesh]

Yes we are doing it now but after yesterday's issue, we plan to change it in v5.2.

[Ritesh]

Added for v5.2.

[Ritesh]

Added for v5.2.

[Ritesh]

Float and double datatypes are known to have such issues.

Try issuing the following query on both the Linux and Windows machines.

SELECT FORMAT(id, 0) FROM tablename1;

In my testing on Windows I received the following:

mysql> SELECT format(id, 0) FROM tablename1;

+

---

+

| format(id, 0) |

+

---

+

| 9,999,100,476,915,712 |

+

---

+

This shows that number provided is not stored exactly when using FLOAT. How/what is stored depends upon both the Operating System and the CPU. More on this can be found in the documentation at http://dev.mysql.com/doc/mysql/en/problems-with-float.html

This is general problem with floating point types. They are:

1) Stored as approximate values

2) Platform dependent

Besides everything floating point types should be *never* used as a Primary Key not even as a part of a WHERE clause.

[Ritesh]

RC3 at http://www.webyog.com/forums/index.php?sho…9745&#entry9745 fixes this issue. Can you confirm it?

[Ritesh]

Fixed in RC3 development tree.

[Ritesh]

Looks like a BUG coz in Result Tab it is working perfectly. Will be fixed in RC3, which is another 5 hours away.

[Ritesh]

We dont use BLOB column for WHERE clause. As far as I remember, SQLyog only uses PRIMARY KEY if its available. I will check it up again now.

If a TABLE has PK, then SQLyog should not make any attempt to use other column.

Is the key PK or UNIQUE KEY because we dont consider UNIQUE KEY as PK. We plan to change it in v5.2 but not now.

@vygi: Can you post the CREATE TABLE statement of your table?

[Ritesh]

Can somebody confirm the bug fix?

[Author]

Posts