Bug #53886 | Incorrectly says cannot import tables when reverse engineering | ||
---|---|---|---|
Submitted: | 21 May 2010 13:45 | Modified: | 8 Feb 2013 16:28 |
Reporter: | Stephan Hodges | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.21 RC | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | wrong warning/error message |
[21 May 2010 13:45]
Stephan Hodges
[21 May 2010 14:40]
Johannes Taxacher
Hello Stephan, the error about too many tables is shown because WB refuses to automatically create a diagram containing more than 250 tables (the option is activated by default). it will not prevent you from importing the objects into your document (and maybe create one or several diagrams out of your imported objects manually later). If you go through the wizard and click "execute" the warning is displayed and the checkbox to auto-create the diagram is cleared - now you can click execute to proceed without the option. (if this works for its expected behavior)
[21 May 2010 20:14]
Stephan Hodges
Thanks for the explanation. However it does say it **cannot** import the tables, but what you are saying is that it won't do it automatically. The message should (IMO) be changed in that case. Also, if, say, I had an 8 GB 64 bit system, wouldn't 277 table be a fairly small and easy to handle import? On my system, with 3 GB and 32 bit, it took less than 10 seconds to handle it all. But, as you say. I confess I didn't search the manual for this point before "reacting"...
[25 May 2010 9:53]
Susanne Ebrecht
You are totally right, the error message should get changed.
[8 Feb 2013 16:28]
Armando Lopez Valencia
No reproducible in the latest WB Version Verified in: Ubuntu 12.04x64 Windows7x64 WB 5.2.46 rev.10385