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 #71392 Incosistent recommendations whether to use mysqli_free_result()
Submitted: 2016-01-16 19:47 UTC Modified: 2020-12-13 15:33 UTC
From: marcgala at hotmail dot com Assigned: dharman (profile)
Status: Closed Package: MySQLi related
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: marcgala at hotmail dot com
New email:
PHP Version: OS:

 

 [2016-01-16 19:47 UTC] marcgala at hotmail dot com 
Description:
------------
http://php.net/manual/en/mysqli-result.free.php explicitly claims that:
"You should always free your result with mysqli_free_result(), when your result object is not needed anymore."
However, both examples at http://php.net/manual/en/mysqli-stmt.get-result.php use mysqli_result and do never call any variant of mysqli_free_result().
This is inconsistent.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2016-12-31 18:44 UTC] cmb@php.net
-Package: Documentation problem +Package: MySQLi related
 [2020-12-13 15:33 UTC] dharman@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: dharman
 [2020-12-13 15:33 UTC] dharman@php.net 
Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at
http://www.php.net/downloads.php

The misleading note was removed. Thanks for pointing it out. 
PR: https://github.com/php/doc-en/pull/240
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Thu Apr 18 16:01:29 2024 UTC