Java Persistence’s TABLE_PER_CLASS Is Evil
TL;DR – TABLE_PER_CLASS inheritance strategy uses some of the most inefficient ways to query. Your database performance will be dragged down as the data grows — consider switching to JOINED.
Tagged in
Jpa
Java User Group (Malta)
Discussing all things Java/Scala/Groovy in both startups and enterprise alike. Have a great article you would like to share? Get in touch with us!
More informationFollowers
More, on Medium