-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Deprecate mysqli_kill #11926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate mysqli_kill #11926
Conversation
Same comment as #11929 |
On this, it seems the functionality isn't deprecated in MariaDB, as far as I can see from a quick search anyway. It doesn't mean it needs to be kept in PHP of course (and if the behaviour will differ based on server version, potentially that is justification for its removal by itself), but it does seem there are some subtle differences between |
@kamil-tekiela could you rebase this PR? |
c52f58a
to
4512d82
Compare
8abed8e
to
9235de7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if CI is green
Co-authored-by: Jan Rosier <[email protected]>
Co-authored-by: Jan Rosier <[email protected]>
9235de7
to
562f184
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I'm confused why there is an SPL arginfo file change
You know, I actually didn't see it there. I just run the gen_stub and committed. I'll remove it from this PR. |
562f184
to
346d75b
Compare
MySQL 5.7 has deprecated
COM_PROCESS_KILL
which is used under the hood by mysqli. See:I understand it may be controversial for PHP, but we shouldn't support commands that are deprecated in MySQL. The only problem with this is that the way that PHP tests used this function is actually problematic. When we use
mysqli_kill
to kill our own process there's no error, but when we use SQLKILL
then we get an error about aborted query. It makes sense, but creates a problematic upgrade path. Not sure if there's a way to deal with this.We could emulate that command in mysqlnd, but that's an undesirable solution.