Don't touch parent timestamps, just this once.

Josh Pike — Thu, 26 Jan 2023 17:51:54 +0000

I have a couple models related to each other. We'll call them Parent and Child. Here's the child...

class Child extends Model
{
  protected $touches = ['parent'];

  public function parent()
  {
    return $this->belongsTo(Parent::class);
  }
}

I ran into a situation where I create the parent model, save it to the db, then loop over some inputs, creating the children. But if that takes long enough (it usually does), the parent’s updated_at no longer matches its created_at. This was an issue for me because I'm showing the user an icon if the db record has been updated. With actual updates to the children, I want it to happen, but on the initial save, I don’t.

Laravel includes a couple undocumented ways to not touch the parent timestamps, even when you've set up your model to do so.

The base Model includes a static method to turn off the touching.

/**
 * Disables relationship model touching for the current class during given callback scope.
 *
 * @param  callable  $callback
 * @return void
 */
 public static function withoutTouching(callable $callback)
 {
   static::withoutTouchingOn([static::class], $callback);
 }

Although it didn't strike me as terribly intuitive, in my case I can toss this in the controller method responsible for saving a form.

$parent = new Parent();
// set some props...
$parent->save();

foreach ($request->input('child-data') as $childData) {
  Parent::withoutTouching(function() use ($parent) {
    $child = new Child();
    $child->parent_id = $parent->id;
    $child->data = $childData;
    $child->save();
  }
}

This works to keep the creation of child records from updating the parent's updated_at value. Nice!

There is another, and in my opinion, much simpler way to accomplish this. The base Model's save() method accepts an optional $options array as an argument. As far as I can tell, there is currently only one $options key that the framework checks for. Lucky for us, it allows us to turn off touching!

Instead of nesting the child logic inside the callback of the static method, you can just pass an options array to the save method

$parent = new Parent();
// set some props...
$parent->save();

foreach ($request->input('child-data') as $childData) {
  $child = new Child();
  $child->parent_id = $parent->id;
  $child->data = $childData;
  $child->save(['touch' => false]);
}

This one seems more intuitive to me, and definitely less complicated. Nicer!

Hi, I'm Josh Pike

Josh Pike — Thu, 04 May 2017 01:17:24 +0000

I have been coding for 5 years.

You can find me on GitHub as heidilux

I live in Dexter.

I work for MedHub

I mostly program in these languages: PHP.

I'm building an api for a startup mobile app with Laravel

, Cheers!

Forem: Josh Pike

Don't touch parent timestamps, just this once.

Laravel includes a couple undocumented ways to not touch the parent timestamps, even when you've set up your model to do so.

Hi, I'm Josh Pike