| Bug #16717 | Close but no cigar Schema Name allowed e.g Market vs market | ||
|---|---|---|---|
| Submitted: | 23 Jan 2006 1:31 | Modified: | 1 Dec 2006 14:24 |
| Reporter: | Jerry OBrien | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
| Version: | 1.1.19 | OS: | Windows (Windows XP) |
| Assigned to: | Mike Lischke | CPU Architecture: | Any |
| Tags: | Object Editors | ||
[23 Jan 2006 11:28]
MySQL Verification Team
Thank you for the bug report.
[1 Dec 2006 14:24]
Mike Lischke
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/
Description: If the schema name is market, QB allows one to connect with the spelling - - - -Market. But if one creates a stored procedure while connected with the 'wrong' schema name it is not shown in QB nor is it usable. Albeit - - it appears that one can do most other task to the 'correct' schema when this happens. The stored procedure is cataloged in both ROUTINES table of infomation_schema and procs table of mysql with the schema name of 'Market'. How to repeat: Create a schema called "market" with one "table". Connect to the schema with MYSql Query Browser with the Default Schema name "Market". (You will be allowed to connect and you will see the table that was created under the 'market' name. In QB create a Stored Procedure using the "Scripts" menu option and the "Create Stored Procedure / Function" - options with a simple select * from "table". Assuming the there are no errors, the stored procedure will be created but will not display under the schema as a normal stored procedure would. You cannot drop this stored procedure with a simple - - - - drop procedure `ProcName` One must use - - - - drop procedure `Market`.`ProcName` Suggested fix: Either don't allow one to connect with an incorrect schema name or treat the schema name variation the same as the correct name.