[wp-trac] [WordPress Trac] #21663: Use PDO or mysqli for MySQL queries when available

[WordPress Trac]

#21663: Use PDO or mysqli for MySQL queries when available
------------------------------+------------------
 Reporter:  scottconnerly     |       Owner:
     Type:  task (blessed)    |      Status:  new
 Priority:  normal            |   Milestone:  3.9
Component:  Database          |     Version:  3.5
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:
------------------------------+------------------

Comment (by Otto42):

 Replying to [comment:174 adegans]:
 > But it will force devs to improve and get with the times.

 You get more flies with honey than with vinegar.

 A better long term way would be:

 1. Migrate: Start including experimental support for the new methods on a
 limited basis, with planned expansion of the methods later. This also lets
 you modify the methods later if it turns out you have to do so, without
 breaking huge amounts of new development based on it.

 2. Teach: Find the most common dependencies that will break because of it
 on those cases. Make documentation somewhere detailing these cases, and
 providing examples of how to change the dependent code effectively.

 3. Notify: Make a list of code that will be affected, mass email the
 authors, point them to said documentation and other resources.

 4. Deprecate: After sufficient time or after enough measurable migration
 has occurred, deprecate support for the older methods, stop using old
 methods by default, but perhaps with sufficient backwards compatibility to
 make some cases not break totally, or to otherwise minimize impact to
 users.

 Any big change has to be this way. You can't just break the world because
 it's the right thing to do, because it's never really the right thing to
 do.

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