Doc #67112 [Opn->Csd]: Notes in conflict with each other
| From: | mazzanet@php.net | Date: | Fri, 13 Jun 2014 16:09:15 +0000 |
| Subject: | Doc #67112 [Opn->Csd]: Notes in conflict with each other | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-11277@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=67112&edit=1
ID: 67112
Updated by: mazzanet@php.net
Reported by: tomkinsr at istop dot com
Summary: Notes in conflict with each other
-Status: Open
+Status: Closed
Type: Documentation Problem
Package: Documentation problem
Operating System: Windows, Mac, Linux
PHP Version: Irrelevant
-Assigned To:
+Assigned To: mazzanet
Block user comment: N
Private report: N
New Comment:
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().
Previous Comments:
------------------------------------------------------------------------
[2014-04-23 00:32:21] 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.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=67112&edit=1