[wp-trac] [WordPress Trac] #16091: Replace current DB class with a robust standardized DB abstraction layer

[WordPress Trac]

#16091: Replace current DB class with a robust standardized DB abstraction layer
-----------------------------+----------------------
 Reporter:  sc0ttkclark      |       Owner:
     Type:  feature request  |      Status:  closed
 Priority:  normal           |   Milestone:
Component:  Database         |     Version:  3.1
 Severity:  major            |  Resolution:  wontfix
 Keywords:  4.0              |
-----------------------------+----------------------

Comment (by sc0ttkclark):

 You're saying that the Core team has no plans to do this - currently -
 however I'm slating this for a 4.0 discussion, which is further ahead and
 assuming WP grows to a point in which MySQL-only support becomes an
 unnecessary barrier. Simply building custom WPDB classes and plugging them
 in, or creating short term solutions that don't solve the larger root
 issues seems to me to be something that should be up for discussion within
 core.

 Is there a specific reason this ticket must remain closed beyond being
 something not currently planned? Or can the subject of this ticket even be
 discussed in depth by Core developers and contributors without the burden
 of the dead ended 'closed' / 'wontfix' ticket? I don't want to get into a
 close/reopen war on this ticket. :)

 '''This ticket represents a cultural shift within WP Core to become more
 database agnostic in it's query syntax and DB abstraction - whether that
 be replacing or methods of overhauling the current WPDB implementation.'''

 4.0 is quite a while a way and I believe discussion and attention is
 merited to increase the interoperability and expansion of WP.

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