Computer scienceBackendSpring BootSpring DataSpring Data JPAJPA Entities

Mapping inheritance

Optimizing disk memory

Report a typo

Our pottery studio is doing well. But after a while, we realize that our server doesn't have a lot of disk space left. So we decided to change our inheritance strategy for the Potter entities. Which one should we use if performance is not crucial for us?

Select one option from the list

Single table

Mapped Superclass

Table per Class

Joined

___

Create a free account to access the full topic