Bug #96712 | In Alter Table right clicking on any row gives an error | ||
---|---|---|---|
Submitted: | 31 Aug 2019 0:26 | Modified: | 1 Oct 2019 19:30 |
Reporter: | Peter Sayers | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 8.0.17 | OS: | Windows |
Assigned to: | CPU Architecture: | x86 |
[31 Aug 2019 0:26]
Peter Sayers
[31 Aug 2019 0:35]
Peter Sayers
Restarting MySQL workbench does not help
[31 Aug 2019 16:52]
MySQL Verification Team
Thank you for the bug report. Please provide the create table statement, the MySQL server version and exactly Windows OS version. Thanks.
[31 Aug 2019 17:35]
Peter Sayers
This problem happens on all tables on all databases using the instance of MWB on my main computer (8.0.17). It does not happen on my other computer running 6.3.5. Below is a sample create statement. If I'm feeling brave later I will upgrade MWB on my other computer to 8.0.17: CREATE TABLE `purchase_invoice` ( `purchase_invoice_id` int(11) NOT NULL AUTO_INCREMENT, `mill_id` int(11) DEFAULT NULL, `supplier_id` int(11) DEFAULT NULL, `customer_id` int(11) DEFAULT NULL, `invoice_date` date DEFAULT NULL, `invoice_ref` varchar(45) DEFAULT NULL, `shipment_id` int(11) DEFAULT NULL, `order_id` int(11) DEFAULT NULL, `due_date` date DEFAULT NULL, `payment_date` date DEFAULT NULL, `purchase_type_id` int(11) DEFAULT NULL, `value_usd` decimal(10,2) DEFAULT NULL, `value_rmb` decimal(10,2) DEFAULT NULL, `comment` varchar(255) DEFAULT NULL, `deleted` char(1) DEFAULT 'N', `notes` varchar(255) DEFAULT NULL, PRIMARY KEY (`purchase_invoice_id`) ) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=latin1;
[1 Sep 2019 19:30]
MySQL Verification Team
Thank you for the feedback. I couldn't repeat you have not informed which MyDQL Server version are you using and Windows OS. Thanks.
[2 Oct 2019 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".