php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #69334 Microseconds vs Milliseconds confusion
Submitted: 2015-03-31 01:47 UTC Modified: 2015-04-03 17:03 UTC
From: webmaster at thedigitalorchard dot ca Assigned: jmikola (profile)
Status: Closed Package: mongo (PECL)
PHP Version: 5.6.7 OS: OS X 10.10
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 you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: webmaster at thedigitalorchard dot ca
New email:
PHP Version: OS:

 

 [2015-03-31 01:47 UTC] webmaster at thedigitalorchard dot ca
Description:
------------
---
From manual page: http://www.php.net/class.mongodate
---

The documentation states that the MongoDate class stores milliseconds, but then the class definition defines "sec" (seconds) and "usec" (micro-seconds) properties. This should be clarified or corrected. There are 1000 microseconds in 1 millisecond, so the class should be storing sufficient data to represent both units, but the documentation should indicate this better.

Test script:
---------------
n/a

Expected result:
----------------
Documentation should reflect class definition.

Actual result:
--------------
Documentation talks about milliseconds where as class definition defines microseconds.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2015-04-03 17:03 UTC] jmikola@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: jmikola
 [2015-04-03 17:03 UTC] jmikola@php.net
Thanks for reporting this issue. Development for the "mongo" extension and its documentation are primarily managed through our JIRA project, so I've opened https://jira.mongodb.org/browse/PHP-1428 to track this issue.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved.
Last updated: Wed Jan 15 08:01:29 2025 UTC