Closed (fixed)
Project:
Drush
Component:
Core Commands
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
22 Dec 2010 at 03:31 UTC
Updated:
6 Jan 2011 at 02:10 UTC
Jump to comment: Most recent file
I have MySQL configured in such a way that MySQL can't drop the database but it can drop the files. drush v3 happily ignored ERROR 1010 (HY000) at line 1: Error dropping database (can't rmdir './drupal7m', errno: 16) but v4 insists on not continuing. Commenting out the return drush_set_error(dt('Could not drop and create database: @name', array('@name' => $db_name)));
in ./commands/core/site_install.drush.inc makes it work again.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | drush-si-drop-tables.patch | 3.28 KB | greg.1.anderson |
Comments
Comment #1
greg.1.anderson commentedThe set error should just be a log 'error', or perhaps a log 'warning'.
Comment #2
greg.1.anderson commentedActually, if the create db failed, or if the database exists but contains junk, then bad things might happen in site-install. This patch falls back to _drush_sql_drop, which drops all tables, if the drop db / create db operation fails. If _drush_sql_drop also fails, then site-install aborts as before.
Comment #3
moshe weitzman commentedI like it. RTBC.
Comment #4
greg.1.anderson commentedCommitted