Bug #22156 DROP SCHEMA test_db; damages informations about table TEST_DB.t1
Submitted: 9 Sep 2006 5:52 Modified: 20 Sep 2006 8:12
Reporter: Georg Richter Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version:5.2 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[9 Sep 2006 5:52] Georg Richter 
Description:
1. There will be no problem, if the SCHEMA names differ in more than
   upper/lower case characters.
2. Though the DROP SCHEMA test_db seems to damage some informations
   about TEST_DB.t1, even a session started just after the DROP SCHEMA test_db
   is able to SELECT on TEST_DB.t1.

How to repeat:
part of the test protocol:
CREATE SCHEMA test_db;
CREATE SCHEMA TEST_DB;
CREATE TABLE TEST_DB.t1 (f1 INTEGER) ENGINE = jstar;
DROP SCHEMA test_db;
# The preceeding DROP SCHEMA test_db; damages somehow the informations
# about the table TEST_DB.t1.
# I get here query 'DROP SCHEMA TEST_DB' failed: 1051: Unknown table 't1'
DROP SCHEMA TEST_DB;
   ERROR 42S02: Unknown table 't1'
[9 Sep 2006 5:52] Georg Richter 
was mantis bug #174

Jim Starkey: There is an outstanding inconsistence between Falcon, the SQL standard and traditional MySQL handling of case sensitivity of identifiers, which I consider unresolved. This test demonstrates the problem. Until the greater issue is resolved, this should remain an outstanding bug/problem.
[20 Sep 2006 8:12] Calvin Sun 
dup of bug#22216.
[4 Nov 2006 16:51] Calvin Sun 
sorry, should be bug#22166.