YTDB - Показать сообщение отдельно - [12947] Update game_event table structure to use better time format

**newsbot** · 15.12.2016, 22:56

Автор: cala

<pre style='white-space:pre-wrap;width:81ex'>[12947] Update game_event table structure to use better time format

This brings two fixes:
1- change the start_time and end_time columns to use DATETIME format
instead of timestamp. Timestamp is stored as an absolute time and is
subject to time zone changes, shifting the effective start/end time of
an event. Thanks to @Neotmiren for pointing and providing a fix. This
closes https://github.com/classicdb/database/issues/764
2- Change the default value for start_time and end_time column to UNIX
origin of time. The previous zero value was not compliant with SQL
strict mode, thanks @kartoffelsup for reporting. Moreover, it has no
meaning time-wise and could lead to some bad code. This closes
https://github.com/cmangos/classic-db/issues/15</pre>

Подробнее...

15.12.2016, 22:56	#1
newsbot News Bot Регистрация: 20.11.2009 Сообщений: 1,290 Сказал(а) спасибо: 0 Поблагодарили 5 раз(а) в 5 сообщениях	[12947] Update game_event table structure to use better time format Автор: cala <pre style='white-space:pre-wrap;width:81ex'>[12947] Update game_event table structure to use better time format This brings two fixes: 1- change the start_time and end_time columns to use DATETIME format instead of timestamp. Timestamp is stored as an absolute time and is subject to time zone changes, shifting the effective start/end time of an event. Thanks to @Neotmiren for pointing and providing a fix. This closes https://github.com/classicdb/database/issues/764 2- Change the default value for start_time and end_time column to UNIX origin of time. The previous zero value was not compliant with SQL strict mode, thanks @kartoffelsup for reporting. Moreover, it has no meaning time-wise and could lead to some bad code. This closes https://github.com/cmangos/classic-db/issues/15</pre> Подробнее...