Bug #7450 drop database does not drop all tables on the database
Submitted: 21 Dec 2004 9:18 Modified: 3 Feb 2005 15:09
Reporter: paulo vieira Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:3.23.58 OS:Linux (fedora core 2)
Assigned to: CPU Architecture:Any

[21 Dec 2004 9:18] paulo vieira 
Description:
if I create a database with the following commands, then when I issue the drop database command the database is not dropped  because the table tipo_pessoa is not dropped. If I change the name of table in the command procedure to tip_pessoa then everything works good.

drop database if exists badagru;
create database if not exists badagru;
use badagru;
CREATE TABLE pessoa(`n_pessoa` INT NOT NULL AUTO_INCREMENT,
                   `nome` VARCHAR(100),
                   `n_tipo_pessoa`  INT DEFAULT 0,
                   `dt_nascimento`  DATE,
                   `n_pai`  INT DEFAULT 0,
                   `n_mae`  INT DEFAULT 0,
                   `n_enc_educ`  INT DEFAULT 0,
                   `n_filiacao`  INT DEFAULT 0,
                   `n_morada`  INT DEFAULT 0,
                    PRIMARY KEY `PrimaryKey` (`n_pessoa`));
CREATE TABLE tipo_pessoa(`n_tipo_pessoa` INT NOT NULL AUTO_INCREMENT,
                   `descricao` VARCHAR(50),
                    PRIMARY KEY `PrimaryKey` (`n_tipo_pessoa`));
INSERT INTO tipo_pessoa (n_tipo_pessoa, descricao) VALUES (1,'Campo Vazio');

How to repeat:
It's easy to repeat, if you run the procedure two times, the second time mysql will not be able to drop the database and it gives the following error:

ERROR 1050 at line 14: Table 'tipo_pessoa' already exists

Suggested fix:
I think the problem is connected to the name of table is prefixed to "tipo_" when I chenge it to "tip_"  the problem desapears.
[23 Dec 2004 14:35] MySQL Verification Team 
Hi,

Thank you for the report, but I can't repeat it with the above commands.
What is your locale settings?
[23 Dec 2004 15:22] MySQL Verification Team 
Looks like you hit the same bug as #3594.
Could you upgrade MySQL server to the recent 4.0 and check if the problem still exists?
[3 Jan 2005 15:09] paulo vieira 
I installed version 4.1.8 standard and now its ok.

Thanks.
[14 Feb 2005 22:54] Bugs System 
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".