[wp-trac] [WordPress Trac] #33501: Starting w/ WP4.2, upgrade scenario may fail for non-MySQL installs

[WordPress Trac]

#33501: Starting w/ WP4.2, upgrade scenario may fail for non-MySQL installs
--------------------------+--------------------
 Reporter:  RSkoon        |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:
Component:  Database      |     Version:  4.1.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+--------------------

Comment (by RSkoon):

 Thanks all for looking into this and responding...

 My thoughts were along the same line as @pento in that a fix was needed to
 wp-db.php because this was something that appeared to be added to the WP
 Core to support a non-MySQL scenario.  Starting with 4.2.x upgrades in
 this code path started to cause failures mentioned above.

 w.r.t. the fix that I chose, I tried to limit the scope to where the
 problem(s) were specifically happening.  There are other places in the
 code that are specifically looking, perhaps expecting, is_mysql to be
 null, so I thought just adding the extra check here was safer.

 Thanks for the discussion...
 Rob

--
Ticket URL: <https://core.trac.wordpress.org/ticket/33501#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform