Bugs item #3516089, was opened at 2012-04-09 06:15
Message generated for change (Tracker Item Submitted) made by mongo02
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3516089&group_id=23067
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Interface
Group: 3.4.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brent (mongo02)
Assigned to: Nobody/Anonymous (nobody)
Summary: DROP does not work on defective VIEWs
Initial Comment:
This is the same bug reported in bug #1764195, but still exists. If a table is modified or dropped, which makes the view defective, the view cannot be dropped using the DROP TABLE command, which the interface generates. A defective view can only be dropped using the DROP VIEW command in the SQL tab. The interface should use DROP TABLE for tables and DROP VIEW for views instead of DROP TABLE for both.
Additional info:
A defective view shows "in use" in the table list under the Records, Type, Collation, Size, and Overhead columns.
If the table and non-defective view are dropped at the same time (using checkboxes and "With selected: DROP"), the view is dropped successfully (using DROP TABLES).
If the DROP button (red X) is used on the defective view, a NOTICE of "#1051 - Unknown table '<view_name>'" is generated (using DROP TABLE).
If the "With selected: DROP" option is used on the defective view, an ERROR of "#1051 - Unknown table '<view_name>' is generated (using DROP TABLE).
Configuration:
phpMyAdmin - 3.4.5
PHP - 5.3.10
MySQL - 5.1.61
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=377408&aid=3516089&group_id=23067
|