Bug #91982 | MySQL workbench takes fforever to load data | ||
---|---|---|---|
Submitted: | 11 Aug 2018 22:00 | Modified: | 13 Sep 2018 7:18 |
Reporter: | Robert Kiker | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 8.0 | OS: | Windows |
Assigned to: | CPU Architecture: | x86 |
[11 Aug 2018 22:00]
Robert Kiker
[13 Aug 2018 7:18]
MySQL Verification Team
Hello Robert, Thank you for the report. I tried to reproduce with WB 8.0.12 and local MySQL instance, 30+ columns and some dummy data but with no luck. May I request to please provide exact table and import file to reproduce this issue at our end? Thank you. If the data you need to attach is more than 3MB, you should create a compressed archive of the data and a README file that describes the data with a filename that includes the bug number (recommended filename: mysql-bug-data-91985.zip) and upload one to sftp.oracle.com. Your Oracle Web account (rkiker@carolina.rr.com) and a client that supports SFTP are required in order to access the SFTP server. To upload the file to sftp.oracle.com: Open an SFTP client and connect to sftp.oracle.com. Specify port 2021 and remote directory /support/incoming/. Log in with your username (rkiker@carolina.rr.com) and password. Upload the archive to /support/incoming. Once you have uploaded the file, add a comment to this bug to notify us about it. Example: sftp -oPort=2021 -oUser=rkiker@carolina.rr.com sftp.oracle.com:/support/incoming Usage Notes: This directory is unlistable, which means that once you have uploaded your file, you will not be able to see it. A file cannot be uploaded more than once with the same filename. The filename must be changed before attempting to upload the file again. The filename should always start with mysql-bug- prefix. Files are retained on the SFTP server for 7 days and then permanently removed. Thank you for your interest in MySQL regards, Umesh
[14 Sep 2018 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".