php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #47592 mysql_result() under-dcoumented
Submitted: 2009-03-07 17:51 UTC Modified: 2009-11-19 11:52 UTC
From: bruce at kaskubar dot com Assigned:
Status: Wont fix Package: Documentation problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
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: bruce at kaskubar dot com
New email:
PHP Version: OS:

 

 [2009-03-07 17:51 UTC] bruce at kaskubar dot com
Description:
------------
The formal Note, "Calls to mysql_result() should not be mixed..." is interesting but not particularly helpful.

Expected result:
----------------
All behaviors related to function use should be documented. For instance, it seems that using mysql_result affects the result set row pointer such that a subsequent use of mysql_fetch_array does not begin where one may expect. Other behaviors may be involved. Once recorded as a bug (at http://bugs.php.net/bug.php?id=12023), the undocumented behaviors are apparently considered features.

Users of mysql_result should be warned that it includes undocumented behaviors. The Note's "should not" should be restated, emphatically, as an outright prohibition where quantifiable behavior is an expectation of its use.

Actual result:
--------------
Documentation unbecoming of serious understanding.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2009-11-19 11:52 UTC] vrana@php.net
Why the calls should not be mixed is internal PHP thing.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu May 02 16:01:29 2024 UTC