One of the benefits of using JPA and Hibernate is that it provides an abstraction of database-specific dialects and features. So, in theory, you can implement an application, connect it to one of the supported databases and it will run without any code changes.
Hibernate does that really well. But let’s be honest, you didn’t expect that your application will run perfectly with every supported database, did you?
Hibernate handles the most important things. But if you want your application to perform well, you still need to know which database(s) you want to use and adjust your configuration and code accordingly.
In one of the previous posts, I talked about 6 things you need to know if you want to use
Hibernate with a PostgreSQL database. And today I want to
have a closer look at the MySQL database.