Master Hibernate and JPA with Spring Boot in 100 Steps - Step 79 - Using Enums with JPA

The video tutorial discusses the drawbacks of using strings for review ratings and suggests using enums instead. It explains how to create an enum for review ratings, refactor methods to use enums, and update getters and setters. The tutorial also covers storing enums in a database, initially as ordinals, and later recommends using strings for better database design. The video concludes with a demonstration of the changes in the H2 console.

Why is using a string for review ratings not recommended?

• It is not compatible with databases.

• It is too complex to implement.

• It is more expensive to store.

• It can lead to data corruption.

What is the first step in refactoring a method to use enums?

• Change the method name.

• Update the method documentation.

• Add a new parameter to the method.

• Change the method signature to use enums.

What annotation is used to specify that a field is an enum?

• @EnumField

• @EnumType

• @Enumerated

• @EnumValue

What is the default way of storing enum values in a database?

• As binary data

• As ordinals

• As strings

• As JSON objects

What is a potential issue with storing enums as ordinals?

• It increases storage size.

• It complicates data retrieval.

• It can lead to incorrect data if enums are reordered.

• It requires additional indexing.

Why is it better to store enum values as strings in a database?

• It enhances data security.

• It simplifies database queries.

• It prevents issues when adding new enum values.

• It reduces storage costs.

What happens to existing data when a new enum value is added if ordinals are used?

• Existing data is automatically updated.

• Existing data is deleted.

• Existing data remains unaffected.

• Existing data may become incorrect.