Andrew Brown
Andrew Brown
@taylorotwell shoot, I knew there was something in my original post I forgot that I wanted to add. As far as I can tell, there would be no breaking changes...
yah, while related, the database config `timezone` option is out of scope of this PR. and actually, switching to `datetime` types makes it all moot anyway.
> As a rule of thumb, use timestamp for marking something like an event that has happened in the world or application (created_at, updated_at, disabled_at, credited_at, etc.). Use datetime when...
> If the average user understands the differences or has the need to use this or that, he will change it in his project. I would argue the average user...
> You provided 0 evidence or statistics about how users use this framework. Fair point. I meant my numbers as hyperbole rather than statistic. I thought that was obvious, but...
What are your concerns? Would love to address them if I could. I think I've shown from a technical standpoint `datetime`s are superior for the majority of Laravel users, but...
any updates?
one more bump
any update on this?
is there any interest from the maintainer(s) for these grammar and spelling fixes?