Menu
In my development project, I am using JPA (hibernate) as OR Mapping technology for database access. I sometimes hit performance issues and technical difficulties when I map DB table to entities directly for complex relationship.
I find a workaround is to map DB view to JPA entities. This make coding easier and sometimes performance is better. Do you think it is a anti-pattern of using JPA in this way?
696
In JPA you can map to a VIEW the same as a table, using the @Table annotation. You can then map each column in the view to your object's attributes. Views are normally read-only, so object's mapping to views are normally also read-only.
The JPA specification requires the @Entity annotation. It identifies a class as an entity class. You can use the name attribute of the @Entity annotation to define the name of the entity. It has to be unique for the persistence unit, and you use it to reference the entity in your JPQL queries.
We can create a SQL query with the @Query annotation by following these steps: Add a query method to our repository interface. Annotate the query method with the @Query annotation, and specify the invoked query by setting it as the value of the @Query annotation's value attribute.
This is not a workaround and not an anti-pattern. There is a topic on mapping JPA Entities to SQL Views. It gives you enough information whether to use this method or not.
Personally, I prefer Java classes, and thus I use Result Classes Constructor Expression. It instantiates and populates objects of provided class based on results query return.
You can view both of these methods which increases performance and reduces structure complexity.
122
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
