Bug #56658 Float division error when trying to dump database
Submitted: 8 Sep 2010 15:43 Modified: 13 Oct 2010 15:58
Reporter: Luke Georgalas Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S2 (Serious)
Version:5.2.27 CE OS:Windows (7 x64)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: Administration, dump, float division

[8 Sep 2010 15:43] Luke Georgalas
Description:
I've got a Windows 7 x64 machine as my client, and Ubuntu 10.04 x86 as my database server. I have MySQL 5.1.41-3ubuntu12.6 running on the server, and I'm using MySQL Workbench 5.2.27 CE on my client node. I'm able to connect to my database server just fine (database-only mode for now, no SSH-based remote administration). When I select the Data Dump tab, my database schemas do not appear. The connection seems fine because I can see the server health and connections list. When I select the Data Dump tab, in the log box at the bottom, it says: "Error updating DB: float division". Every time I press Refresh, another instance of that error appears in the log box.

How to repeat:
Start MySQL Workbench. Connect to remote Linux server in database-only mode. Select Data Dump tab.
[8 Sep 2010 15:46] Luke Georgalas
Screenshot (png)

Attachment: Workbench.png (image/png, text), 110.49 KiB.

[8 Sep 2010 15:48] Alfredo Kojima
Do you have any databases in the server? Does the user you connect from have access to them?

The float division error has been just fixed, but it only happens when you have no dbs in your server.
[8 Sep 2010 16:19] Luke Georgalas
I do. I have a bugzilla database, and I have another database I'm building myself.
[8 Sep 2010 16:21] Luke Georgalas
The user I'm connecting with is root, who should be able to see all the databases, right? Remote root was enabled on the server (server is not visible outside my home network). I didn't see anywhere that disables or enables that root access explicitly, but I did add a root@myclientmachine entry on the server, which allowed me to connect.
[14 Sep 2010 22:24] Sveta Smirnova
Thank you for the feedback.

Please connect as same user, but using SQL Editor Tab, then type query SHOW DATABASES and send us its output.
[15 Sep 2010 13:14] Luke Georgalas
I performed the 'show databases' command and all that returned was information_schema. So I then tried to use the command line client to connect to the server and got the same thing back when issuing a 'show databases' command, just information_schema. This appears to be a server issue and not a workbench issue. Though it would be nice if the client game a more accurate error message instead of just float division error.
[15 Sep 2010 13:49] Luke Georgalas
So my original problem turned out to be solved by granting privileges to 'root'@'%'. Now the workbench works fine. I just would not have known that by the error message I got from the workbench. I don't know if you guys want to leave this issue open and address that error message (maybe add a permissions test before trying to access that information and report a permissions problem to the user if it exists), or if you want to just dismiss this bug report.
[27 Sep 2010 15:18] Alfredo Kojima
The float division error is already fixed. The problem of the account not having enough privileges to see the databases you want is not detectable, or at least can't be told apart from an account that is limited on purpose.
[13 Oct 2010 10:41] Johannes Taxacher
Fix for "float division" error confirmed in release 5.2.29
[13 Oct 2010 15:58] Tony Bedford
An entry has been added to the 5.2.29 changelog:

In the Administrator, clicking on the Data Dump tab generated the error Error updating DB: float division and schemata were not displayed.