Shulou(Shulou.com)06/01 Report--

Editor to share with you how Laravel does not trigger updated_at changes, I believe most people do not understand, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

Modification of updated_at is not triggered

Whenever an Eloquent record is modified, the updated_at field is automatically maintained with the current timestamp, which is a great feature.

But sometimes you don't want to do this, for example, when you increase a value, you don't think it's a "whole row update."

So, you can do everything as above-- just disable timestamps and remember that this is temporary:

$user = User::find (1); $user- > profile_views_count = 123 leading user-> timestamps = false;$user- > save (); this is all the content of the article "how Laravel does not trigger changes to updated_at". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.