Well, according to the book I'm reading, MySQL data type 'timestamp' only goes up to year ``` 2038-01-18 22:14:07.999999 ``` What's the purpose of using 'timestamp' data type, when it only goes up to year 2038-01-18?
Well, according to the book I'm reading, MySQL data type 'timestamp' only goes up to year ``` 2038-01-18 22:14:07.999999 ``` What's the purpose of using 'timestamp' data type, when it only goes up to year 2038-01-18?
other databases have limits too — Postgres [can't store anything beyond the year 5874897](https://stackoverflow.com/questions/36446248/maximum-date-that-can-be-stored-in-postgres)
Thanks Peter, I now understand the point of your comment. ;)
@@@ wikipedia 0b457ed96791b430dddb95fc6eaa9758f2b4823e3fccd415c3c906e74eb73660 hsf "Year 2038 problem" "The Year 2038 problem relates to representing time in many digital systems as the number of seconds passed since 00:00:00 UTC on 1 January 1970 and storing it as a signed 32-bit integer. Such implementations cannot encode times after 03:14:07 UTC on…"
see also IPv4, "[running out of identity values](https://www.google.com/search?q=running+out+of+identity+values)", and (probably more directly relevant to your underlying question) the unix epoch end problem ;-)
not to be snarky - but the point is to store timestamps with a value less than or equal to the limit. running over the limit is a thing that's happened before, will happen again, and isn't limited to the MySQL platform specifically or timestamp data generally.
@@@ wikipedia 2c1ef1b71f7378b9c3de03738a172f96029dca87b874bb3fd3b0d54c04cae058 hru "Year 2000 problem" "The Year 2000 problem, also known as the Y2K problem, the Millennium bug, Y2K bug, the Y2K glitch, or Y2K, refers to events related to the formatting and storage of calendar data for dates beginning in the year 2000. Problems were anticipated, and ar…"