Master Hibernate and JPA with Spring Boot in 100 Steps - Step 33 - ManyToOne Mapping - Wrapping Up

The video tutorial explores fetching strategies in database relationships, focusing on one-to-many and many-to-one associations. It explains lazy and eager fetching, demonstrating how they affect data retrieval. The tutorial also covers the use of transactional contexts to manage persistence and concludes with a brief introduction to many-to-many relationships.

What is the default fetching strategy for a one-to-many relationship in JPA?

• Immediate fetching

• Batch fetching

• Eager fetching

• Lazy fetching

Why is a transaction necessary when using lazy fetching?

• To maintain the persistence context

• To avoid database locks

• To ensure data is fetched eagerly

• To improve query performance

What happens when eager fetching is used in a one-to-many relationship?

• The related entities are fetched on demand

• Both the main entity and related entities are fetched

• The main entity is not fetched

• Only the main entity is fetched

In a many-to-one relationship, what is the default fetching strategy?

• Immediate fetching

• Batch fetching

• Eager fetching

• Lazy fetching

How can you retrieve a course from a review in a many-to-one relationship?

• Using a direct SQL query

• By calling review.getCourse()

• By using a separate repository

• By fetching all reviews first

What is a key consideration when choosing between eager and lazy fetching?

• The size of the database

• The number of users

• The specific use case and performance needs

• The programming language used

What type of relationship will be discussed next after one-to-many and many-to-one?

• One-to-one

• Hierarchical

• Many-to-many

• Self-referencing