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

go to bug id or search bugs for

Bug #32502 time/timestamp return
Submitted: 2005-03-30 14:24 UTC Modified: 2005-04-07 01:00 UTC
Votes:2
Avg. Score:4.0 ± 1.0
Reproduced:2 of 2 (100.0%)
Same Version:1 (50.0%)
Same OS:0 (0.0%)
From: daviscabral at gmail dot com Assigned:
Status: No Feedback Package: InterBase related
PHP Version: 4.3.10 OS: Linux (Slackware)
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: daviscabral at gmail dot com
New email:
PHP Version: OS:

 

 [2005-03-30 14:24 UTC] daviscabral at gmail dot com 
Description:
------------
Yesterday, our systems was update.
PHP that was 4.3.7 went to 4.3.10.
After this, data from database returns wrong.
I believe that is a problem with extension.

My problem is exactly with the SQL instruction (the code is exctaly the same): 

SELECT MOD_ID, MOD_NOME, MOD_SIGLA, MOD_HRINIMANHA, MOD_HRFINMANHA, MOD_HRINITARDE, MOD_HRFINTARDE, MOD_TEMPOMAX FROM MODULO WHERE MOD_ID = 9999

Return in 4.3.7
9999 | 4 | Diversos | DIV | 09:00:00 | 12:00:00 | 13:30:00 | 18:00:00 | 06:00:00

Return in 4.3.10
9999 | 4 | Diversos | DIV | 17:39:24 | 17:39:24 | 17:39:24 | 17:39:24 | 17:39:24



Reproduce code:
---------------
SELECT MOD_ID, MOD_NOME, MOD_SIGLA, MOD_HRINIMANHA, MOD_HRFINMANHA, MOD_HRINITARDE, MOD_HRFINTARDE, MOD_TEMPOMAX FROM MODULO WHERE MOD_ID = 9999

Expected result:
----------------
Return in 4.3.7
9999 | 4 | Diversos | DIV | 09:00:00 | 12:00:00 | 13:30:00 | 18:00:00 | 06:00:00

Actual result:
--------------
Return in 4.3.10
9999 | 4 | Diversos | DIV | 17:39:24 | 17:39:24 | 17:39:24 | 17:39:24 | 17:39:24

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-03-30 17:13 UTC] sniper@php.net 
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.
 [2005-04-07 01:00 UTC] php-bugs at lists dot php dot net 
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 [2005-09-15 09:15 UTC] Andres dot Lilla at ra dot ee 
timestamp field fails between years 1881-1901. I am using php4.3.11, firebird1.5.2 and FedoraCore3. Firebird and isql work fine and give a right result. php works fine to year 1881 and at year 1902 to today. All timestamp field values between years 1881-1901 are constantly 12/13/1901 22:45:52
with php4.1.2 all is right and OK
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Apr 19 10:01:28 2024 UTC