Bug #51345 | change in comment field reversed | ||
---|---|---|---|
Submitted: | 20 Feb 2010 12:45 | Modified: | 4 May 2010 18:23 |
Reporter: | Be Wa | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.15Beta Rev 5053 | OS: | Windows (xp) |
Assigned to: | CPU Architecture: | Any | |
Tags: | comment field, reversed |
[20 Feb 2010 12:45]
Be Wa
[20 Feb 2010 12:47]
Be Wa
No reversing of the change takes place when I close the bottom-area with the properties-tab of that table and reopen it by double-clicking on the table.
[23 Feb 2010 8:33]
Susanne Ebrecht
Many thanks for writing a bug report. Unfortunately, I am not able to follow you. Please describe step by step how we can reproduce this.
[24 Feb 2010 14:14]
Be Wa
See the screenshot: I use a model with already existing tables and add some characters to the comment shown in the left field [1]. So I add an "a" to the already existing "b". Then I click into the right field [2], nothing happens (except for that it get the focus...), it still shows the old comment ("a"). Then I click into the left field, the previous entry "ab" is reversed to "a".
[24 Feb 2010 14:16]
Be Wa
See the screenshot: I use a model with already existing tables and add some characters to the comment shown in the left field [1]. So I add an "a" to the already existing "b". Then I click into the right field [2], nothing happens (except for that it get the focus...), it still shows the old comment ("a"). Then I click into the left field, the previous entry "ab" is reversed to "a".
[24 Feb 2010 14:18]
Be Wa
screenshot of the two textfields for comments
Attachment: mysql.png (image/png, text), 23.70 KiB.
[4 Apr 2010 18:23]
Valeriy Kravchuk
Please, check with a newer version, 5.2.17, and inform about the results.
[4 May 2010 23: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".