On 31/03/2015 12:20, Larry Martell wrote:
On Tue, Mar 31, 2015 at 1:13 AM, Andrew Moore <eroomy...@gmail.com> wrote:
When you use a timezone with DST there is no such thing as 2.30am on the
date of changeover. That hour doesn't exist.
I am using UCT - I am not using a timezone.
In MySQL 5 and above, TIMESTAMP values are converted from the local
server time to UTC at storage and then back again at select. So if the
local server is using a DST timezone, then your TIMESTAMP value will
always reflect local DST.
Look up the difference between timestamp and datetime data types.
I did do that before I posted, but it wasn't really clear to me, but I
think I need to use a DATETIME instead of a TIMESTAMP. Correct?
Yes.
As a highly-rated comment on StackOverflow puts it:
"Timestamps in MySQL generally used to track changes to records, and are
often updated every time the record is changed. If you want to store a
specific value you should use a datetime field."
http://stackoverflow.com/questions/409286/datetime-vs-timestamp
As a more general rule of thumb, use DATETIME unless you have a specific
application for which you know that TIMESTAMP is more appropriate.
They're not interchangeable, and not intended to be.
Mark
--
http://www.markgoodge.uk
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
