Re: `COM_RESET_CONNECTION` support in `mysqlnd`
| From: | Eric Norris | Date: | Sun, 03 May 2026 14:14:35 +0000 |
| Subject: | Re: `COM_RESET_CONNECTION` support in `mysqlnd` | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-130753@lists.php.net to get a copy of this message | ||
On Sun, May 3, 2026 at 8:01 AM Tim Düsterhus <tim@bastelstu.be> wrote:
>
> A single RFC with two primary votes to independently resolve each of the
> two cases (at the same time) would work. Given the concerns and the
> similarity between both, I don't think we can do without an RFC.
Fair enough. I'd appreciate your collaboration on this RFC if you're
amenable! I've started a draft here:
https://wiki.php.net/rfc/min_supported_versions_php_8_6.
I have a few things to note:
- I wasn't sure how to approach the merger of the two topics. I
decided to model this like the various deprecation RFCs, in that we're
deciding on a slate of minimum supported software for PHP 8.6.
- Ideally, if people objected to the MySQL minimum version for
persistent connections, I'd be able to include a vote that allowed for
an INI setting.
- Related to that: I'm not sure how much detail to add about the
actual implementation I'd like for persistent connections. Is this a
vote for my specific implementation, or just the higher-level concept
of requiring a certain version of software in PHP 8.6? My goal is to
ship this, so needing to do two RFCs back-to-back would be annoying.
Feel free to respond privately if you'd like to take this off-list. Thanks!