Why is NOW UTC incorrect time format? It has worked fine before!

[StevenM]

I have never seen this error before but it is now coming up and stopping me saving any date time. I have this throughout my app.

How do I fix this?

status	"500"
code	"ER_TRUNCATED_WRONG_VALUE"
message	
stack	"Error: ER_TRUNCATED_WRONG_VALUE: Incorrect datetime value: '2021-07-28T22:45:53Z' for column 'date_created' at row 1

[mebeingken]

Recent change. If you have your server setup as UTC, then you should be able to use NOW instead.

Alternatively, you can continue with NOW_UTC but append with a replace formatter to remove the “Z”.

NOW_UTC.replace(‘Z’,’’)

Make sure to use standard single quotes, not any ridiculous quotes iOS has inserted in my post.

[StevenM]

Thanks @mebeingken

That’s gong to be a pain in the… but thanks for the fix!

Why Have the NOW_UTC at all if its not working out of the box argggg

[Teodor]

Saving data to database causes error

In PHP it was always been the way that the NOW_UTC returns the date with a Z at the end, in NodeJS we fixed this in last update. The Z indicates the timezone in the ISO 8601 standard. MySQL still doesn’t support timezones, you pass a localtime and internally it converts that to an UTC time. You could strip off the Z when you want to store it like that.