| Bug #88112 | MySQL Workbench Changing Storage to Virtual after it was previously set to Store | ||
|---|---|---|---|
| Submitted: | 16 Oct 2017 18:23 | Modified: | 17 Oct 2017 7:35 |
| Reporter: | Jay Jaeger | Email Updates: | |
| Status: | Won't Fix | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
| Version: | 6.3.9 | OS: | Windows (10 X64) |
| Assigned to: | CPU Architecture: | Any | |
[17 Oct 2017 7:35]
MySQL Verification Team
Hello Jay Jaeger, Thank you for the report and feedback! Thanks, Umesh
[14 Sep 18:04]
Omer Barnir
Posted by developer: This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained. MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation. Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.
Description: When modeling using MySQL Workbench, I am having problems were the workbench will change the "Storage:" for a column from Virtual after I had already set it to "Stored" and saved the model. How to repeat: Create a model with two tables. Create a column "firstKey", data type INT, Primary Key, Non Null, Unique, Generated and change "Storage" from Virtual to "Stored". In the second table, create whatever key ("secondKey") you like. Create another column "firstKey" and make that a foreign key that refers back to the first table. Make sure that the first table still says "Stored" and save the model. Reopen the model. Sometimes (not 100%) the "Storage" will have been changed back to "Virtual". Suggested fix: Stop doing that. ;)