Error running database seeder about laracon2018 HOT 4 CLOSED

This is caused by a little quirk in MySQL's timezones interpretation. Datetime values are not interpreted directly as UTC, but first assumed to be the timezone determined by your system, and then converted to UTC. I kept getting that error as well, but only for March dates in different years - and they always coincided with daylight saving, at early morning hours (quite strangely it didn't matter if it was North American, or European dayligt saving).

More on the issue here: https://stackoverflow.com/a/25855998/4171578 (including the comments).

I was able to fix it by going to MySQL and executing this command:

SET GLOBAL time_zone='+0:00'

from laracon2018.

That's really weird. 2011-03-13 02:27:30 is a totally valid date, and really that just gets generated by Laravel anyway via the model timestamps. Sorry, I've got nothing. I'd start Googling. 😞

from laracon2018.

Okay for sure. I think it might have something to do with the Mysql version on my home machine. I got past it using mysql version 5.7 but then ended up with

SQLSTATE[42000]: Syntax error or access violation: 1305 FUNCTION laracon2018.to_char does not exist (SQL: select count(*) as aggregate from `customers` where `birth_date` is not null and to_char(birth_date, 'MMDD') in (0409, 0410, 0411, 0412, 0413, 0414, 0415) and `sales_rep_id` = 1)

Going to leave this open in case anyone else experiences this or has other insights, if you don't mind!

from laracon2018.

@amadeann Awesome! Thanks for sharing this.

from laracon2018.