inwoker

@xicond TIMESTAMP is limited to the year of 2038 @terabytesoftw Do I understand it correctly that you want me to write code and submit it for PR? If it's that,...

@lubosdz @mtangoo My arguments for `DATETIME` We don't know how our software will be used in the future and for how long. Maybe at some point it will become part...

@mtangoo I did some research. Yeah, you're right. `BIG INT` is more futureproof than `DATETIME`. At least in current versions of sql software. It goes much beyond 9999-12-31, the maximum...

@mtangoo I already said how it's more usable. So do you use INT for date fields in your projects? 1) Yes, being able to look at which date the migration...

@rob006 1) there is migrate/history. But it doesn't affect that browsing migrations through DB would be more convenient if it's changed to DATETIME 2) what exact tools and solution will...

@bizley you're against changing the field to BIG INT? Or only against changing it to DATETIME? As for yii2 existing in 2038, I'm pretty sure it will. I encounter projects...