So I couldn't find a Drupal specific documentation about this, and I know this is far off into the future, but it seems to me the way we currently use timestamps in Drupal will invoke the 2038 bug right about when our kids graduate college.
I hope I am missing the obvious here, but looking at node table for example all created and updated timestamps are not 'unsigned' integers. According to this SE post and this mysql issue having timestamps as unsigned integers kicks the ball down the road for several generations till 2116 (when I assume there won't be a need for CMS because we will all know everything) so... shouldn't we be using unsigned integers?
