Re: Question about date()

From: Date: Tue, 07 Oct 2008 12:08:37 +0000
Subject: Re: Question about date()
References: 1 2 3  Groups: php.general 
Request: Send a blank email to php-general+get-281530@lists.php.net to get a copy of this message
On 7 Oct 2008, at 12:48, Jason Pruim wrote:
On Oct 7, 2008, at 7:41 AM, Stut wrote:
On 7 Oct 2008, at 12:38, Jason Pruim wrote:
I am trying to track down an error and can't seem to figure it out... Here is the error out of my log: [Tue Oct 7 07:31:43 2008] [error] PHP Warning: date() expects parameter 2 to be long, string given in /Volumes/RAIDer/webserver/Documents/dev/stimecard/timecard.php on line 57 Here is line 57: $timeout = date("m/d/y h:i:s A", $row['timeout']); And the info that is trying to grab from the database is: +------------+------------+-------+--------+-------------------+
| timein     | timeout    | empID | record | Name              |
+------------+------------+-------+--------+-------------------+
| 1222354037 | 1222382837 |     1 |    107 | Jason Pruim       |
+------------+------------+-------+--------+-------------------+ Now... the error only happens on line 57... On line 56 there is the same command except: $timein = date("m/d/y h:i:s A", $row['timein']); And that doesn't cause any errors so I'm at a bit of a loss as to what to do? I know I can redirect the warning to an error message, but I don't want to do that... I am trying real hard to write clean code... And this is my last error... It's a total cosmetic thing since it still displays everything right... Any ideas? :)
Do a var_dump($row['timeout']) on the line before the one giving the warning to check that it contains what you think it does.
Hey Stut, Thanks for the quick response... You were right... I did a var_dump both on $row['timein'] and $row['timeout'] and the error was because of the way that I update the records. for time in, I insert a new record, for time out, I update the record where timeout= NULL and THAT is what was causing the issue... I guess I can just redirect that error, ignore it, or come up with a different way to update the current record without having to use NULL, or maybe, write a timeout timestamp for like midnight on January 1 1955 or something like that...
Try "is null" rather than "= null". -Stut -- http://stut.net/

« previous php.general (#281530) next »