Level 80
@abhishek-jetani Why are you placing validating checks in a database transaction in the first place? You should be validating your data before you even attempt to use any values in a database statement.
4 likes
Aug 7, 2024
6
Level 1
Laravel 11 DB Transaction and Validation Order Issue
I'm working on a Laravel 11 application and have a question regarding the order of database transactions and validation checks in a controller function.
In my controller function, if I place DB::beginTransaction(); at the beginning of the function, before performing validation, the validation errors do not show up in the Blade view. However, if I place DB::beginTransaction(); after the validation checks, the validation errors are displayed as expected.
This issue only occurs in Laravel 11. Can someone explain why this happens?
Level 1
Hi, @martinbean
Thank you for your observation. I am aware that validating checks are typically performed before attempting any database operations. However, in this particular project, the validation and transaction logic were structured together, and this approach worked seamlessly in Laravel 10 and earlier versions.
In Laravel 11, I am encountering issues where database transactions seem to interfere with the proper display of validation error messages in Blade view files. I would like to understand if this behavior is due to a bug or if there have been any changes in the database transaction methods in Laravel 11.
I appreciate any insights or recommendations you can provide on this matter.
Level 104
@Abhishek-Jetani are you also using the database for the Session?
Level 80
I appreciate any insights or recommendations you can provide on this matter.
@Abhishek-Jetani I gave you my insight and implicit recommendation: perform validation on the data before attempting to use that database in a database query.
1 like
Level 1
@tykus Yes
Level 1
@abhishek-jetani Thank you. I'm facing the same issue. Can anyone help me with this?
1 like
Please or to participate in this conversation.