MySQL Bugs: #24812: Double clicking unicode(fullstop) table ommits gravel characters

Bug #24812	Double clicking unicode(fullstop) table ommits gravel characters
Submitted:	5 Dec 2006 3:42	Modified:	5 Dec 2006 11:39
Reporter:	Jared S (Silver Quality Contributor)	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.6 BETA	OS:	Windows (WinXP)
Assigned to:		CPU Architecture:	Any
Tags:	fullstop, gravel

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
Hi.  When I double click a table with the (.) fullstop character in it, QA fails to wrap table name up in gravel chracters and then causes script to fail.

How to repeat:
1. Create db1
2. Create table called my.table (id field only)
3. Double click newley created table

Suggested fix:
Ensure that when a table with "." is doubled clicked, the the auto generated query is correctly wraped in gravel characters `for.example`

Thank you for the bug report. Please read the Manual about restrictions
in identifiers names

http://dev.mysql.com/doc/refman/5.0/en/legal-names.html