Hi
On 7/18/26 01:34, Eric Norris wrote:
I don't know if the cost is "just a few conditionals." We'd have two
paths with a PDO option:
[…]
I don't like either of these options, and as the RFC author I feel
that the best outcome is to choose the "correct" choice, especially
considering that we are talking about software that is a decade old.
While I can appreciate your argument, I don't think that the pool of
affected users is large enough to warrant anything less than this.
I agree with the entire quoted email, and particularly the last
paragraph. The “shared nothing” request model of PHP is a huge selling
point to make the code easy to reason about and prevent a whole class of
bugs. I would consider it a bug that persistent connection can introduce
mutable state that outlives a given request and thus supporting and
using COM_RESET_CONNECTION is a bugfix in spirit to me.
I also find it a reasonable expectation from PHP users, and particularly
companies, that when they want to benefit from the latest and greatest
PHP that they also keep the rest of their stack current. For the
COM_RESET_CONNECTION case the only expectation is that they use a MySQL
or MariaDB version that is not EOL. In fact according to EU law such as
the GDPR, using software that is no longer supported by updates is
extremely risky, since it very likely contains known and unfixed
security vulnerabilities. My understanding is that there are other
compliance frameworks - such as PCI - that effectively mandate using
“maintained software” as well.
Best regards
Tim Düsterhus
