MySQL Bugs: #6255: DROP DATABASE bug on Mac OS X

Bug #6255	DROP DATABASE bug on Mac OS X
Submitted:	25 Oct 2004 20:51	Modified:	2 Dec 2004 7:25
Reporter:	Adriaan van Os	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.5-gamma	OS:	MacOS (Mac OS X 10.2.8)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Consider the following pseudo code: 
  
 Init 
 Connect 
 CREATE DATABASE 
 SelectDB 
 repeat INSERT INTO 
 DROP DATABASE 
 Close 
  
 Now, things get really absurd. When running this code multiple times client-server, the 
number of records (rows) increases. That is, DROP DATABASE removes all files from disk (I 
checked that), but records (rows) are not removed from (I guess) the server cache. 
  
 This happens on Mac OS X 10.2.8 with the mysql 4.1.5-gamma binary distribution. It 
doesn't seem to happen on Windows (XP). 
  
 Regards, 
  
 Adriaan van Os

 

How to repeat:
See above.

Suggested fix:
Think before you write code.

I haven't been able to reproduce this.

Can you please add a working script that can be used to reproduce the problem?

Hi,

Thanks for your bug report!

I haven't been able to repeat this problem.  Do you have a way which you can repeat this 
problem every time?

This is the type of thing I was doing with the query cache enabled:

mysql> create table mytest( id int not null );
Query OK, 0 rows affected (0.00 sec)

mysql> insert into mytest values (1), (2), (3), (4), (5);
Query OK, 5 rows affected (0.00 sec)
Records: 5  Duplicates: 0  Warnings: 0

mysql> select * from mytest;
+----+
| id |
+----+
|  1 |
|  2 |
|  3 |
|  4 |
|  5 |
+----+
5 rows in set (0.00 sec)

mysql> drop table mytest;
Query OK, 0 rows affected (0.00 sec)

mysql> create table mytest( id int not null );
Query OK, 0 rows affected (0.01 sec)

mysql> select * from mytest;
Empty set (0.00 sec)

I believe that's the type of thing you're describing.  I was doing this with 4.1.7 on 10.2.8.

Best Regards

Thanks for your comment and for looking into this. I wanted to write a small testprogram to 
reproduce this, but at the moment I don't have the time to do so (next month I have more 
time than now). I used libmysqlclient_r.a rather than the command line interface (if that 
makes any difference.

I see that in your test you used DROP TABLE rather than DROP DATABASE (without a DROP 
TABLE).

Regards,

Adriaan van Os

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