i think letting mysql handle date to auto set on create should be slower than setting it your self as a string, but this latency is very very very small, you won't feel any difference at all.
i would recommend letting the db handle timestamps for you. for create and update. some extra work off your shoulders.
as i also answered a few seconds ago in the other topic, im going to use laracasts russian doll caching, thats using the updated_at column, is the whole eloquent standard of using the updated_at still working then? Bart
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast