WordPress.org

Make WordPress Core

Changes between Initial Version and Version 11 of Ticket #31018


Ignore:
Timestamp:
01/17/2015 06:01:03 PM (5 years ago)
Author:
SergeyBiryukov
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31018

    • Property Keywords has-patch needs-testing added
    • Property Status changed from new to reopened
  • Ticket #31018 – Description

    initial v11  
    11WordPress currently does not allow support for persistent database connections. This can be accomplished by prepending "p:" to the hostname with mysqli however with its current configuration WordPress will be confused by the ":" and think the hostname is actually a port if specified in the wp-config.php file. This patch add support for a constant that allows persistent connections to be turned on or off.
    22
    3 Why should this be added to core? Because persistent connections are useful :P. But really, we have seen requests for this in other tickets such as https://core.trac.wordpress.org/ticket/27933. Additionally I am involved in a project where 10,000+ sites are requiring persistent db connection, not an insignificant number. Persistent db connections are also needed to ensure proper performance on IIS and Azure installations.
     3Why should this be added to core? Because persistent connections are useful :P. But really, we have seen requests for this in other tickets such as #27933. Additionally I am involved in a project where 10,000+ sites are requiring persistent db connection, not an insignificant number. Persistent db connections are also needed to ensure proper performance on IIS and Azure installations.
    44
    55In short a couple lines of code is all it takes to ensure WordPress continues to work well across other platforms and project requirements.