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. > 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? > > On 31 Mar 2015 05:43, "Larry Martell" <larry.mart...@gmail.com> wrote: >> >> I have a column that was a timestamp type. I was inserting rows using >> NOW(). When we switched to DST and the hour from 2am to 3am was >> non-existent I of course had no data for that hour. For reasons I >> don't need to go into, that missing hour caused problems downstream. >> To prevent this from happening next year I changed the insert to use >> UTC_TIMESTAMP() and I wanted to fill in data for that missing hour. >> But no matter what I do it will not let me insert values for that hour >> - it gives me an 'Invalid TIMESTAMP value' warning" and inserts a row >> with a time of 3:00 for any time in that hour I give. This makes me >> think that I have not actually solved the problem for next year (I >> can't test this to know). >> >> So my questions are: >> >> 1) How can I actually insert a timestamp value that will not be >> affected by the time change and not have the missing hour? >> 2) Why is it not allowing me to insert UTC times for that missing >> hour? How can I insert UTC values for that missing hour? >> >> >> TIA! >> -larry >> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe: http://lists.mysql.com/mysql >> > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
