The most powerful way to use Eloquent

[@nexxai]

Wow. This is awesome! It makes so much sense regarding consistency and I think I'm going to be spending some time over the next week bringing it into my latest side project. Thanks for doing this!

Let me know what you think!

[@DaviMartins99]

I wish that Taylor left you some feedback on why not merging this instead of just closing with the auto message, guess it was because it's pretty big change to the Eloquent-way of thinking. Great idea for a package nevertheless, can see myself pulling this if the right scenario comes up.

I think it was a fair response! Eloquent is very complex and it’s a critical piece, so I understand that changing how it behaves is complicated.

[@piter33]

Great idea, Mateus! I'll try it. I think this is worth a PR in Laravel 😉

The package came from a PR! :-) github.com/laravel/framework/pull/48914

[@mahdibouguerzi]

Great video 👍 ! but what will i miss if i used DB::transaction ?

You’d have to save each “piece” of the aggregate as separate entities, individually

[@the-code-reviewer]

Great Doctrine idea :)

[@inspiway6424]

Nice, I had no idea about that "persist" method. Thx!

[@criley7755]

It's not a native Laravel function, it's part of his own package that he mentions throughout this video. Laravel does have a "push" method which can save a model and its relationships at the same time.

[@neverything]

Great video Mateus, thanks for sharing

Glad you enjoyed it my friend!

[@gui1gear]

What shortcuts are you using in phpstorm with vim?

Mostly just jumping lines

[@gui1gear]

Não fui bem claro kkk… Queria saber se você mudou os shortcut da ide, pois no meu phpstorm ele fica avisando que tá dando conflito de shortcuts por causa do plugin do vim.

@@gui1gear não mudei nada não, que tipo de shortcut vc tá falando? eu entro no normal mode e uso os comandos do vim normalmente

[@joshcirre]

This is awesome. Thanks for teaching me. :)

Thanks for watching my dude!

[@LileshJadav]

How about increased memory Usage? Because most developers don’t think about optimisation.

Memory usage would be the same as persisting each model individually.

[@Ruggie1of1]

push() exists on models already and is intended to save the model and relationships. (still a good idea to call it inside of a transaction)

Sadly it doesn’t always work - push assumes that models have been persisted already. See: github.com/laravel/framework/issues/48914

[@bobbyiliev_]

Great video! Well done!

Glad you liked it Bobby!

[@gAAAia]

Amazing !!!!!! Foultzz

[@vladvasilov]

nice! This is somehow similar to MikroORM persist

Oh cool! I’ll check it out.

[@florisvandenberg7424]

This is basically the datamapper pattern inside the activerecord pattern. Horrible. I really, really, really, really hate Eloquent and Laravel as a whole.