Hibernate creates different column alias name for the same query when classes are added to or removed from the persistence unit
Issue
- Hibernate generates different column aliases for the same query in some cases when classes are added to or removed from the persistence unit.
- This requires update of database execution plans when the persistence unit is altered.
- How does Hibernate assign column aliases?
- Is there a way to control column alias generation for mapped class properties?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP) 7
- Hibernate 5
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.