PHP DateTime __construct() Failed to parse time string (xxxxxxxx) at position x

Question

I had this construction error when trying to creating a new DateTime object using a timestamp:

Exception: DateTime::_construct(): Failed to parse time string (1372622987) at position 8 (8): Unexpected character in DateTime->_construct()

The object creation code is:

$start_date = new DateTime( "@{$dbResult->db_timestamp}" );

Where $dbResult->db_timestamp is a valid unix timestamp taken from a database. The timestamp in question was:

1372622987

I would understand this error for invalid formats being passed, but this is a genuine timestamp.

The reason this is very strange: I since ran a script to create a new DateTime object with the timestamp passed in as a hard coded value, and it reported no errors.

This seems to have been a one off, but I need an explanation if there is one, as I can't afford for this to happen again.

The error you have posted and the code you have posted do not match. The error indicates that the timestamp being passed to the DateTime constructor doesn't have a leading @ on it, while the code you posted shows that it is included. One of those things is inaccurate. — user21926
– user21926, Commented Jul 2, 2013 at 14:05
@SeanBright I can confirm that removing the leading @ produces this exact error: codepad.org/ZPZmXi2x — crush
– crush, Commented Jul 2, 2013 at 14:06
This is very interesting. I can assure that the @ has always been in the code, and as I said, it works at all times except this occurrence. I wonder if it wasn't interpreted as a one off. Do we know of any problems of using {} notation instead of joining them with '.' notation? — Alex
– Alex, Commented Jul 2, 2013 at 14:19

saamorim · Accepted Answer · 2013-07-02 14:00:41Z

100

You should use setTimestamp instead, if you hardcode it:

$start_date = new DateTime();
$start_date->setTimestamp(1372622987);

in your case

$start_date = new DateTime();
$start_date->setTimestamp($dbResult->db_timestamp);

answered Jul 2, 2013 at 14:00

saamorim

3,9251 gold badge19 silver badges22 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Alex Over a year ago

Thanks for your input. The strange thing is my code has worked before and since, it was just a random occurrence..

saamorim Over a year ago

I always try to use the proper methods instead of magic strings. I know that the @ and U can work if properly used, but they require additional parsing by the php processor and if there is a method to set the timestamp, using an integer, then you gain a few microseconds in the process.

Yoker Over a year ago

This is too procedural. This answer is not object orientated. OOP uses constructors. There is a constructor available, so use it. Abani Meher's answer is better, I think.

saamorim Over a year ago

I would agree with you if the DateTime was immutable and if there was a constructor that accepted a timestamp. For me, a solution that clearly defines an interface setTimestamp(int) is preferable to a solution that does accept a magic string, not to mention the performance issues involved.

Primo Over a year ago

Okay, why this works? I had the exact same issue as the OP, and when I used your solution it worked, why?

Rob W · Accepted Answer · 2017-12-21 15:25:20Z

19

Use the createFromFormat method:

$start_date = DateTime::createFromFormat("U", $dbResult->db_timestamp);

UPDATE

I now recommend the use of Carbon

edited Dec 21, 2017 at 15:25

answered Jul 2, 2013 at 13:59

Rob W

9,1621 gold badge32 silver badges50 bronze badges

2 Comments

Rob W Over a year ago

No worries, be sure to check $start_date for validity before using.

Kamafeather Over a year ago

.. that is: $start_date === false (rather than null), since createFromFormat (from what I know) never throws exceptions when failing.

Abani Meher · Accepted Answer · 2013-07-02 13:59:40Z

15

change your code to this

$start_date = new DateTime( "@" . $dbResult->db_timestamp );

and it will work fine

answered Jul 2, 2013 at 13:59

Abani Meher

5943 silver badges17 bronze badges

4 Comments

crush Over a year ago

That's effectively the same thing isn't it?

Abani Meher Over a year ago

@crush - looks same but you can try and see the difference

saamorim Over a year ago

The @ symbol makes all the diference. See php.net/manual/en/datetime.formats.compound.php and see the "Unix Timestamp" entry

Alex Over a year ago

The code has worked as it is, it just failed this once - so hard to pin it down to this

Sam Deering · Accepted Answer · 2015-05-19 06:56:11Z

1

This worked for me.

   /**
     * return date in specific format, given a timestamp.
     *
     * @param  timestamp  $datetime
     * @return string
     */
    public static function showDateString($timestamp)
    {
      if ($timestamp !== NULL) {
        $date = new DateTime();
        $date->setTimestamp(intval($timestamp));
        return $date->format("d-m-Y");
      }
      return '';
    }

answered May 19, 2015 at 6:56

Sam Deering

3681 silver badge7 bronze badges

Comments

Bastien D · Accepted Answer · 2013-07-02 14:02:06Z

0

$start_date = new DateTime();
$start_date->setTimestamp($dbResult->db_timestamp);

answered Jul 2, 2013 at 14:02

Bastien D

1,4752 gold badges15 silver badges31 bronze badges

Comments

pankaj · Accepted Answer · 2024-12-26 16:58:06Z

0

you can use Carbon Method for this. This solution also works for Excel Import using csv file.

Carbon::createFromFormat('d/m/Y', $row['scheduled_start_at'])->format('Y-m-d')

answered Dec 26, 2024 at 16:58

pankaj

1,97026 silver badges37 bronze badges

Collectives™ on Stack Overflow

PHP DateTime __construct() Failed to parse time string (xxxxxxxx) at position x

6 Answers 6

5 Comments

2 Comments

4 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

5 Comments

2 Comments

4 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related