Judging from MySQL documentation at https://dev.mysql.com/doc/refman/8.0/en/datetime.html, it sounds best to use DATETIME rather than TIMESTAMP if you want your database to be future proof. After all 2038 is only 18+ years away. The DATETIME type is used for values that contain both date and time parts. MySQL retrieves and displays DATETIME values ...

It would be nice if one could rewrite this C# snippet: public SortedDictionary<string, UObject> GetObjects() {   SortedDictionary<string, UObject> result = new SortedDictionary<string, UObject>();   using (ReadTransaction xact = namingSchema.ReadTransaction())     foreach (ObjectName.RowType row in ...