hibernate-orm
hibernate-orm copied to clipboard
Hibernate's core Object/Relational Mapping functionality
Add test case to replicate the issue #HHH-14365
https://hibernate.atlassian.net/browse/HHH-13691 In order to create a manipulation query I have to pass the entity class twice because the first time it's not used: ```java CriteriaDelete criteriaDelete = entityManager.getCriteriaBuilder().createCriteriaDelete(User.class); criteriaDelete.from(User.class); ```...
https://www.postgresql.org/docs/8.1/functions-datetime.html#FUNCTIONS-DATETIME-EXTRACT
A potential fix for incorrect cycle detection between insert statement batches, which causes performance degradation when large objects are persisted. https://hibernate.atlassian.net/browse/HHH-14344
https://hibernate.atlassian.net/browse/HHH-14340
Signed-off-by: Jan Schatteman
https://hibernate.atlassian.net/browse/HHH-14255 Not sure if there is a better way for managing the `ProxyFactory` for a `MappedSuperclass` https://github.com/hibernate/hibernate-orm/commit/d948e6d7fa7f8fd6f6e6320464ff9cdc1c13a16f `
This is hardly an optimal solution. And maybe straight up wrong. Ideally we should skip these synthetic properties that were created for join during audit here https://github.com/hibernate/hibernate-orm/blob/master/hibernate-envers/src/main/java/org/hibernate/envers/internal/entities/mapper/MultiPropertyMapper.java#L114 However, for some...
These tests currently fail, but demonstrate HHH-14256. https://hibernate.atlassian.net/browse/HHH-14256