PHP new DateTime() with unix timestamp ignores Timezone for application and also explicit Timezone in constructor

[camohub]

Description

I have an object which have created property like unix timestamp integer. I try to convert this property to DateTime object and supposed the PHP will set up correct Timezone according application settings. Application is Laravel 12 which setting for timezone is correct as I see in a log file. Look at the code:

Log::info((new DateTimeZone(config('app.timezone')))->getName());  // Europe/Bratislava
$row->created = (new DateTime('@' . $row->created), new DateTimeZone(config('app.timezone')));
Log::info($row->created->getTimezone()->getName());  // +00:00  !!!!!

The DateTime constructor completelly ignores second argument. Next code works fine:

Log::info((new DateTimeZone(config('app.timezone')))->getName());  // Europe/Bratislava
$row->created = (new DateTime('@' . $row->created))->setTimezone(new  DateTimeZone(config('app.timezone')));
Log::info($row->created->getTimezone()->getName());  // Europe/Bratislava

PHP Version

PHP 8.2

Operating System

Windows 10

[heiglandreas]

See https://www.php.net/manual/en/datetime.construct.php

Note:
The $timezone parameter and the current timezone are ignored when the $datetime parameter either is a UNIX timestamp (e.g. @946684800) or specifies a timezone (e.g. 2010-01-28T15:00:00+02:00).

[heiglandreas]

Besides that: Your second example is the correct way of doing it as the timestamp by definition is in UTC. So setting the timezone afterwards to whatever timezone you require the DateTime to be in will actually transfer the information into the provided timezone - handling DST and all other issues if provided with a type 3 timezone object.

[camohub]

Hmm its little weird if there is a param in __construct() I think. But ok you are right it is in the documentation for the parameter. Geminy did not notice it....

[camohub]

Thank you.