[wp-trac] [WordPress Trac] #16615: More inline docs needed to explain DB errors esp. dead_db() and effects of WP_DEBUG (was: Inconsistent and un-pluggable handling of db error messages esp. dead_db())

[WordPress Trac]

#16615: More inline docs needed to explain DB errors esp. dead_db() and effects of
WP_DEBUG
--------------------------+------------------------------
 Reporter:  jeremyclarke  |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Comments      |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+------------------------------
Changes (by jeremyclarke):

 * component:  General => Comments


Comment:

 Ugh. I just realized that none of the wpdb::bail() messages show unless
 WP_DEBUG is set to true. This is my fault for not noticing.

 It seems that as long as WP_DEBUG is not true dead_db() does in fact fire
 and use the wp-content/db-error.php file as described.

 Apologies for the noise in the ticket above. I think that all we really
 need at this point is more comments in the source to make it clearer what
 is happening and when. The way it's set up now you'd have to dig around
 forever to realize what's going on.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/16615#comment:1>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software