Bug #26572 | Error in editing sql view defintion, destroys original definiton | ||
---|---|---|---|
Submitted: | 22 Feb 2007 16:16 | Modified: | 23 Feb 2007 16:43 |
Reporter: | Heinz Schweitzer (Gold Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.2.9 | OS: | Windows (XP) |
Assigned to: | Vladimir Kolesnikov | CPU Architecture: | Any |
[22 Feb 2007 16:16]
Heinz Schweitzer
[22 Feb 2007 16:16]
Heinz Schweitzer
v1
Attachment: ScreenHunter_001.jpg (image/pjpeg, text), 122.87 KiB.
[22 Feb 2007 16:17]
Heinz Schweitzer
v2
Attachment: ScreenHunter_002.jpg (image/pjpeg, text), 111.01 KiB.
[22 Feb 2007 23:06]
MySQL Verification Team
Thank you for the bug report.
[23 Feb 2007 16:43]
Vladimir Kolesnikov
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at http://dev.mysql.com/doc/en/installing-source.html
[23 Feb 2007 16:50]
Vladimir Kolesnikov
The following behavior was implemented: 1. if view is renamed, a dialog is shown that asks if the old view should be preserved. if user chooses to drop the old object it will dropped only after successful creation of the new view 2. if view name isn't changed then 'or replace' logics is applied. this is handled by the server and basically should act in a safe way 3, if user explicitly removes 'or replace' clause from view definition he/she will get 'view with such name already exists' error