Junior Code Review: Try-Catch and DB Transactions 

Why is this channel not more popular? All of his content is first class and addresses real world issues!

In my opinion only channel here discusses laravel functions in detail, thank you

Hi!! Thank you so much for your videos, very simple, helpfull and comprensive, from Chile 🇨🇱!!

Bro! I have a year using laravel to créate my projects and your content have been so greate! Thanks

Like this codereview format. Keep it going.

This is great review, I love to see more like this, real case in programming world. May we have big code project review, like from route -> middleware -> service provider -> controller

There is one example where wrapping a simple insert in a transaction could be useful: you can specify a second parameter which allows you to automatically retry the transaction in case it fails due to a deadlock or similar issue.

here I am, one of those juniors lol thanks a lot for the advice!

In first example we don't see a context of this save method on that model. This method could be overriden inside model with some additional sql inserts/updates/deletes. No need to use Carbon::parse, when in model u add date to model property $dates. Same to message attribute - we can use mutator inside model for this. Finally I would prefer using create method over save - sth like Contact::create($request->validated()), but in this case model property $fillable should be added to model with specific fields to save.

I always look forward to when you say the words "Hello Guys", "Posts" and "Request". That sounds so nice! 😊 Is there any way to send you my code or is there somewhere to apply? :)

1:56 also PDOException when saving

I feel if validation is properly done most times db transaction is not necessary.. thats my personal opinion, i use db transaction when i deal with relationship in case a model is deleted while the code is executed... Maybe yo do a tutorial on database concurrency in laravel.. thanks

So amazing, your review are soo good sir. It Just im not understand laravel. I only understand python-django. But still your code review are good

Very useful, thank you Mr.

Thank you for your great content , can you please talk about composed primary key and how we can use them in laravel

Great job, Povilas!

thank you...

Thanks for this video, do you have any video's on a multi-tenant laravel application (each customer has their own database and you switch based on who is logged in)? This could be a nice topic as a video. I personally would like to see how this would all interact with jobs/queues etc...

Was waiting for it

awesome video as always

What if request doesn't have 'email' ? There is no validation for email, but Contact use $request->emal

Thank you a lot for your greate job.Can you tell me what is the color scheme used in your phpstorm?

terima kasih

4:14 i think it should keep that transaction. for something like model events or model observers.

sir i asked question what is the feature of bootstrap with laravel because laravel use taliwind css framework in laravel 8 jetstream

Thanks

Awesome

hi sir any tutorials of implementing event sourcing in laravel application. thanks

Do you post requests on topic somewhere so that people can send in their code specific to that topic?

how in try catch data insert update i use orm

Net Core snob here. PHP SUCKS! Kappa Everyone use they language they prefer and want, I don't care.

no no... in my opinion even redirecting back was too good... they should have straight up logged the user out from the system

Can anyone tell us what is name of this theme on phpstorm?

Благодарю

The single biggest mistake here is that there is business logic and data being processed in a controller.

I always use try/catch/finally for database actions, always. Even a simple transaction like saving a record in a single table can go foul and if it does I want to catch and handle it, I send alerts to the database and use webhooks to send myself a message that something went foul as well. Because I always use ajax to send data and get a return I always use finally so I can let the client app know that things went well or foul to let the user know. I write administrative software for our company and it's a standing joke that when something goes foul I'm going to be at your desk before you've had a chance to close the "an error occurred saving your data" alert. I work with code that was written 18 years ago by someone who was just learning to program so it's still full of really junk spaghetti code and terrible sql, and because there's so much of it I can't rebuild it all I've taken the trouble to go out and wrap entire functions in try/catch/finally just so I know when something goes wrong until I can get to rebuild it. Some of these functions are actually over 3000 lines long and just a mess of if statements and sql that's concatenated one variable at a time into a string before being executed with simple mysqli pass through executes, and while I rebuild as many as I can get to I also have to be constantly adding new functionality, so rebuilding existing code is a downtime effort. As far as transactions for a single row that makes no sense, if it fails there's nothing to roll back