Hibernate N+1 problem and solution | Hibernate Interview Questions and Answers | Code Decode

[@chetankhandave1072]

You are one of the best teacher I have ever seen. Your explanation in such simple language shows your thorough study. Thanks for the video and Best of luck.

[@CodeDecode]

Thanks a lot Chetan 🙂🙂👍

[@arunr8764]

The best explanation I have seen for n+1 problem...

[@CodeDecode]

Thanks Arun

[@nidatariq6992]

Excellent Explanation

[@CodeDecode]

Thanks

[@rajat_singla]

Great explanation. Would be great if you can explain join fetch and entity graphs in detail as you mentioned towards the end of the video. Thanks.

[@CodeDecode]

Sure we will do that Rajat🙂👍

[@ChristForAll-143]

@Rajat singla dude its just sql left join there is nothing special and they are just implementing it via hibernate and spring data dpa - at the end its just left join

[@samuelr-t4d]

thanks for your explanation. This is one of the important interview quuestion

[@CodeDecode]

Thanks 👍

[@vikaskollu]

Thank You. Very Good Explanation.

[@CodeDecode]

You are welcome!

[@gopishettymahindra2713]

Great Explanation . The Best Explanation I have seen for N+1 Problem

[@CodeDecode]

Thanks 😊

[@srisureshshetty]

Very good explanation. Thanks for the tutorial.

[@theprofessor252]

Looking forward to the next video on this.

[@CodeDecode]

Sure Karthik 👍

[@vipulrohilla1383]

Great explanation!!

[@CodeDecode]

Thanks

[@ayushjain7555]

Thanks for this explanation one question if I set fetch type as eager then will this problem arise?

[@sureshmanne7245]

how is the {"listOfEmployees"} referred to Employee table?

[@CodeDecode]

List of employees is actually a list employee entity. Entity maps to relational table. Employee is actually a table in sql

[@48mantusubudhi72]

if we are using fetchType as Eager then the N+1 problem should be fixed right . at the end we are dealing with object creation of realted tables .why do we need so much complications then ?

[@CodeDecode]

Performance is the reason people in It world moves towards lazy loading.

[@ahmedelsabagh6990]

Excellent tutorial!

[@CodeDecode]

Thanks

[@anurani7084]

Great explanation..pls do a video on entity graph

[@CodeDecode]

Sure Anu👍🙂

[@luka.nguyen7]

@Code Decode: I have a question that which is the best-practice to solve N+1 problem, is it entity graph?

[@AshishSingh-rx4sq]

Super demonstration.

[@CodeDecode]

Thanks Ashish 😇👍👍

[@sandysworld7529]

Great explanation.. pls do explain JOIN FETCH and entity graph as well.

[@CodeDecode]

sure we will cover it soon

[@abhilashchaparala7651]

Great explanation. If possible could you please explain entity graphs in detail. Thanks for the video

[@CodeDecode]

Sure 👍Noted 🙂

[@shubhamsamdani3503]

Thanks for this one. please prepare one video for entity graph.

[@CodeDecode]

sure shubham we will upload it soon

[@dmytro4312]

very cool and usefull video, thanks a lot)

[@CodeDecode]

🙂🙂👍👍

[@rohitbagdi5155]

Can I just add fetch type as eager in the entity class and will it do the same ?

[@CodeDecode]

Yepp Rohit

[@phanimc11211]

please explain entity graphs in detail. Thanks for the video

[@syedfaizan5841]

where is the transaction video after propogation i mean you told you will cover transaction isolation

[@18ajai]

Why can't we just use Eager fetch in such scenarios?

[@tannubajpai4782]

Thnx u ma'am

[@CodeDecode]

Thanks Tannu🙂👍

[@amittripathy-kl1cw]

is there any code respository for this code?

[@komal_yadav]

Please tell more on entitygraph

[@CodeDecode]

Sure Komal 👍👍

[@syedfaizan5841]

thanks but please transaction isolation

[@sahilpatil1111]

Thanks, this issue asked multiple times in interview but i have not answered 😑 Pls help in best way to fetch result in custom dto after join non relationship table

[@CodeDecode]

No problem Sahil. Now you know it👍. Sure we will create videos on views and custom dtos 👍

[@Hiteshdua-o6b]

solution start @10:00 min

[@ramprasath4788]

Good

[@CodeDecode]

Thanks

[@satya-b4n]

if we use EAGER instead FETCH in @onetomany annotation will it solve the problem?