DateTime::setTimezone()

date_timezone_set

(PHP 5 >= 5.2.0, PHP 7)

设置 DateTime 对象的时区

说明

设置DateTimeobject的时区。

参数

仅过程化风格：由date_create()返回的DateTime类型的对象。此函数会修改这个对象。

DateTimeZone对象，表示要设置为时区。

返回值

返回被修改的 DateTime 对象，或者在失败时返回FALSE.

更新日志

范例

Example #1DateTime::setTimeZone()例程

面向对象风格

过程化风格

以上例程会输出：

2000-01-01 00:00:00+12:00
2000-01-01 01:45:00+13:45

参见

• DateTime::getTimezone() Return time zone relative to given DateTime
• DateTimeZone::__construct() 创建新的DateTimeZone对象

In response to the other comments expressing surprise that changing the timezone does not affect the timestamp:
A UNIX timestamp is defined as the number of seconds that have elapsed since 00:00:00 (UTC), Thursday, 1 January 1970.
So: with respect to UTC. Always.
Calling setTimezone() never changes the actual "absolute", underlying, moment-in-time itself. It only changes the timezone you wish to "view" that moment "from". Consider the following:

Please note that ALL of these date strings unambiguously represent the exact same moment-in-time. Therefore, calling getTimestamp() at any stage will return the same result: 

The timestamp value represented by the DateTime object is not modified when you set the timezone using this method. Only the timezone, and thus the resulting display formatting, is affected.
This can be seen using the following test code:

As such, you can use this to easily convert between timezones for display purposes.

Surprising that the timezone works only specified in the separated method in case if you'll use ->format('U').
this does NOT apply timezone +0200 in the $timestamp:

this will apply timezone +0200 in the $timestamp: 

doesn't changes timestamp
But

changes timestamp
It is possible to fix that by:

But WTF???

It appears that what forzi at mail333 dot com said is correct.
When you reset the timezone on a DateTime object using a timezone that was instantiated with a GMT offset (e.g. ) the timestamp as reported by  changes. 
However, the value reported by  does _not_ change. Interestingly, once  starts returning the correct timestamp. This appears to be a bug.
In any case, other output values from format() seem to be accurate, and the true timestamp is always accessible via getTimestamp().

I found unexpected behaviour when passing a timestamp.
timezone seems to always be GMT+0000 unless setTimezone() is set. 

鹏仔微信 15129739599 鹏仔QQ344225443 鹏仔前端 pjxi.com 共享博客 sharedbk.com