I have an application database that I'm unable to drop after a period of running several applications against that are using the MySQL++ api.
Wondering if anyone has seen this, if it's a known bug and/or if there is a fix. mysqladmin -uroot -p drop <db> and rm -rf /var/lib/mysql/<dbname> do succesfully remove the database it's just the mysql client has the problem. drop database returns ok but the database is still there (both show databases and ls -al /var/lib/mysql/<dbname> say so). Logging in to mysql with mysql -uroot -p to do the drop so it shouldn't be a user permission issue. The directory permissions and file permissions within seem fine too -rw------- 1 mysql mysql <dirname> The database is largely unpopulated (<10Mb) with about 50 tables (most of which are MyISAM with 2 or 3 HEAP tables). Linux redhat 7.2 rpms ---- MySQL-Max-4.0.1-2 MySQL-4.0.1-2 MySQL-shared-4.0.1-2 MySQL-devel-4.0.1-2 MySQL-client-4.0.1-2 -- Scott Olson --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
