Master Hibernate and JPA with Spring Boot in 100 Steps - Step 36 - ManyToMany Mapping - Fixing Two Join Tables Problem

The video tutorial discusses the implementation of many-to-many relationships between courses and students. Initially, two joint tables are created, which is not desired. The solution involves designating one entity as the owning side of the relationship, though it is less critical in many-to-many relationships due to the use of join tables. The tutorial demonstrates setting the student as the owning side, resulting in a single joint table, student_courses, with student ID and course ID columns. The video concludes with a note on renaming the table and columns for clarity.

What is the main issue with having two joint tables in a many-to-many relationship?

• It leads to data redundancy.

• It complicates data retrieval.

• It increases storage requirements.

• It is not aligned with the desired database design.

In a one-to-one relationship, why is the owning side important?

• It determines which table stores the foreign key.

• It decides the primary key of the table.

• It influences the table naming convention.

• It affects the data retrieval speed.

Why is the owning side less critical in a many-to-many relationship?

• Because a join table is used regardless of the owning side.

• Because it determines the naming of the join table.

• Because it affects only the data retrieval process.

• Because both tables share the same primary key.

What happens when the student is made the owning side in a many-to-many relationship?

• Two joint tables are created.

• A single joint table is created.

• The student table gets a new column.

• The course table gets a new column.

What is the desired naming convention for the joint table in the example?

• courses_students with course ID and student ID

• student_course with student ID and course ID

• course_student with course ID and student ID

• student_courses with student ID and course ID