3 years ago

Category: Laravel, PHP, javascript

· December 3, 2020 · ⋆ Laravel Sometimes, there might be a case where you would want some of the code that lies outside of the transaction to be executed only when the corresponding transaction commits successfully and if in any case, it’s a rollback, that code shouldn’t be executed.

This PR in Laravel v8.17.0 by Mohamed Said introduces a transaction manager class that records transactions, commits, and rollbacks.

Now, you have a code outside of this transaction that you want to be executed once the transaction is committed and discarded when it rolls back.

Execute code outside of transaction only when it commits in Laravel 8.x Artisan command to connect to the database in CLI in Laravel 8.x Throttling submission of form in Laravel Monitor logs in Laravel Telescope in production environment Using MySQL explain for queries in Laravel 8.x Execute code outside of transaction only when it commits in Laravel 8.x Artisan command to connect to the database in CLI in Laravel 8.x Why you should always commit the composer.lock file Exciting new features and improvements in PHP 8 Throttling submission of form in Laravel