正在加载视频...

视频加载失败

If you queue jobs within transactions in Laravel, enable “after_commit” globally to avoid issues. 🫡

16,924 次观看 • 1 年前 •via X (Twitter)

4 条评论

Zoran Stalevski 的头像
Zoran Stalevski1 年前

@laravelphp This begs the question: why isn't it the default setting? Any downsides?

opensourceCM 的头像
opensourceCM1 年前

What’s the cost of mistakes in your contracts? If you work with contracts day-to-day, it’s time to automate. Track every detail, streamline workflows ... ✨ Make managing contracts as easy as a few clicks. Visit our new website & book your demo today!

Luigi G 的头像
Luigi G1 年前

@laravelphp if I enabled globally but want to make an exception ? exists something like commitRightAwayPls?

Floris Andrei 的头像
Floris Andrei1 年前

@laravelphp Spent a whole lot of time last week getting our workers just right. Ended up rewriting a whole lot of the Laravel workers. Idk - feels like they use the wrong abstraction. They should work differently based on different messaging brokers.

相关视频