php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Doc Bug #67112 Notes in conflict with each other
Submitted: 2014-04-23 00:32 UTC Modified: 2014-06-13 16:09 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:0 (0.0%)
From: tomkinsr at istop dot com Assigned: mazzanet (profile)
Status: Closed Package: Documentation problem
PHP Version: Irrelevant OS: Windows, Mac, Linux
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: tomkinsr at istop dot com
New email:
PHP Version: OS:

 

 [2014-04-23 00:32 UTC] tomkinsr at istop dot com 
Description:
------------
---
From manual page: http://www.php.net/mysqli.kill
---

Note on Mysqli::Close says to use Mysqli::Kill first and Note for Mysqli::Kill says to use Mysqli::Close first.

Which is it? Obviously we want a clean process and to recover memory and TCP socket connections on a heavily used server.


Expected result:
----------------
Looking for consistency in the Notes.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2014-06-13 16:09 UTC] mazzanet@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: mazzanet
 [2014-06-13 16:09 UTC] mazzanet@php.net 
This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.

Thank you for the report, and for helping us make our documentation better.

Removed the note on the mysqli.kill page. 
It is not actually possible call kill() after close().
 
PHP Copyright © 2001-2026 The PHP Group
All rights reserved. 		Last updated: Thu Oct 08 09:00:02 2026 UTC