[wp-trac] [WordPress Trac] #6893: Wordpress Database Upgrade Fails Improperly when tables can't be created

[WordPress Trac]

#6893: Wordpress Database Upgrade Fails Improperly when tables can't be created
----------------------+-----------------------------------------------------
 Reporter:  elharo    |       Owner:  anonymous
     Type:  defect    |      Status:  new      
 Priority:  high      |   Milestone:  2.5.2    
Component:  General   |     Version:           
 Severity:  critical  |    Keywords:           
----------------------+-----------------------------------------------------
 When upgrading from 2.2 to 2.5 (probably 2.3 or later) the upgrade will
 fail if the user does not have database permissions to create and drop
 tables. However:

 1. Wordpress does not notice this problem, and attempts to upgrade anyway;
 thus breaking the blog. It should realize it doesn't have permissions and
 not attempt the upgrade, while giving the end user an appropriate error
 message.

 2. WordPress reports success with the upgrade, despite its obvious
 failure.

 3. The upgrade seems to be ignoring SQL errors generated during the
 process. If any SQL errors occur, WordPress should roll back the database
 to its original state.

 This has been discussed on the mailing list and verified as a real problem
 that does occur in practice, despite many devs beliefs that it is
 impossible for this to occur.

 I am not suggesting that Wordpress should be able to upgrade when tables
 cannot be created or dropped. However its error behavior in these and
 similar circumstances needs to be cleaned up.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/6893>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software