When you DROP DATABASE 'base', mysql drops all its tables then drops the db.
At the filesystem, this means deleting all the table files from the 'base'
subdirectory of mysql's data directory, then deleting the 'base directory
itself. If 'base' contains a file that isn't a table file, however, that
file won't be deleted by mysql, which causes the attempt to delete the
directory to fail. Since directory 'base' still exists, mysql sees it as db
'base' still exists. So check in 'base' for any leftover files and either
delete them or move them somewhere else, then try again.
Michael
michael watson (IAH-C) wrote:
Hi
I am running Suse Linux 8.2 and MySQL 3.23.55
A funny thing happens:
%> mysqladmin drop base
Database "base" dropped
%> mysqladmin create base
Can't create database 'base'. Database exists.
And if I log in to MySQL, there it is - undropped!
So why is mysqladmin telling me the database is dropped when it isn't?
Thanks in advance!
Mick
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
