Revise WPDB implementation to use DB agnostic syntax (where possible) and support pluggable DB-specific functions
|Reported by:||sc0ttkclark||Owned by:|
I believe the current DB class, as well as many queries within core of WP outside the DB class, are limiting the growth of WordPress in non-MySQL environments.
I realize that there are existing efforts on behalf of big companies who are using roundabouts to "MacGyver" their way around the problem, but this needs to be solved at the root source which is the DB class used in WP, and the queries used throughout core which contain MySQL-specific SQL.
As an example of a DB abstraction layer we could look into using, check out DBTNG:
You may be familiar with it already if you've ever poked around Drupal. Except this code has been forked from Drupal in the hopes that Drupal and other systems can share it to further each other's abilities. The maintainer of the new project is also someone who works on DBTNG within Drupal core.
I'm hoping this can be looked into and discussed in depth fully before 4.0 rolls around. I realize this is years ahead of time, but such a change I believe requires a great deal of thought, planning, and preparation.
I understand there's no 4.0 milestone yet, so please mark it as Future Release and keep it on your radars.
Change History (19)
- Milestone Awaiting Review deleted
- Resolution set to wontfix
- Status changed from new to closed
5 years ago
- Summary changed from Replace current DB class with a robust standardized DB abstraction layer to Revise WPDB implementation to use DB agnostic syntax (where possible) and support pluggable DB-specific functions