MySQL Bugs: #61315: MySQL crash on select * from <view> after base table is renamed.

Bug #61315	MySQL crash on select * from <view> after base table is renamed.
Submitted:	26 May 2011 21:31	Modified:	26 Jun 2011 22:48
Reporter:	Dennis Dole	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	mysql Ver 14.14 Distrib 5.1.54, for deb	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	crash, rename, table, VIEW

Description:
If the user changes the name of a table used in a view (even just by changing the case of one of the characters in the table's name), then execution of the view will cause MySQL to crash.
If the user edits the view to update the table's name within the view itself, then MySQL will STILL crash on any attempt to execute the view.

How to repeat:
Steps to reproduce:
1. Open MySQL query browser
2. Create a table with data
3. Create a view based on that table (and possibly another).
4. Execute view to confirm proper execution
5. Rename Base table (Just change the case of the first character of the name).
6. Re-run the view.
(Expected Result A)
7. Edit view to fix/update name of table within view. (and save view)
8. Re-run the view.
(Expected Result B)

Expected Result A:
- MySQL should throw an error stating that the table(named in the view) does not exist.
OR
- If MySQL's table names are not case sensetive, MySQL should display the view properly.

Expected Result B:
- Since the view contains the SAME new name as the base table, MySQL should display the view properly.

Actual Result A&B:
- MySQL (or perhaps just MySQL Query Browser) crashes.

Thank you for the bug report. Could you please test the last released version 5.1.57 and if still you get the same issue please provide the test case (create statement, insert date, etc) and no just their description. Thanks in advance.

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".