January 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16038) Fix PersistenceContext.setDefaultReadonly javadoc mistake

by Matías Santurio (JIRA)

Matías Santurio ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63c151a... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZWVmMTM2Nzdj... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16038?atlOrigin=eyJpIjoiZWVmMT... ) HHH-16038 ( https://hibernate.atlassian.net/browse/HHH-16038?atlOrigin=eyJpIjoiZWVmMT... ) Fix PersistenceContext.setDefaultReadonly javadoc mistake ( https://hibernate.atlassian.net/browse/HHH-16038?atlOrigin=eyJpIjoiZWVmMT... ) Issue Type: Improvement Assignee: Matías Santurio ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63c151a... ) Components: documentation, hibernate-core Created: 13/Jan/2023 04:58 AM Priority: Minor Reporter: Matías Santurio ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63c151a... ) Javadoc reads: "Change the default for entities and proxies loaded into this persistence context from modifiable to read-only mode, or from modifiable to read-only mode..." but should be "Change the default for entities and proxies loaded into this persistence context from modifiable to read-only mode, or *from read-only mode to modifiable*..." ( https://hibernate.atlassian.net/browse/HHH-16038#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16038#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:b03f6a4 )

1 year, 12 months

1
0
0 / 0

[JIRA] (HHH-16034) CASE Statement in jpql throws assertion error when running H2 in Oracle mode with OracleDialect

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16034 ( https://hibernate.atlassian.net/browse/HHH-16034?atlOrigin=eyJpIjoiYWE4ZT... ) Re: CASE Statement in jpql throws assertion error when running H2 in Oracle mode with OracleDialect ( https://hibernate.atlassian.net/browse/HHH-16034?atlOrigin=eyJpIjoiYWE4ZT... ) Hello Vijayasaradhi Danda ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , thanks for reporting the issue and providing a reproducer! Your error is caused by wrong OracleDialect version detection due to the database actually being H2. This triggers a compatibility mode for CASE statements in Oracle versions before 9 that doesn’t support grouped predicates like the one in your example ( CURRENT_DATE BETWEEN …). The issue doesn’t occur with Hibernate 6.2.0 since it removed compatibility for Oracle versions < 11.2. Since the final version of 6.2.0 will be released shortly I suggest upgrading to that once it’s available to solve the issue. Another workaround would be creating a custom dialect (e.g. H2OracleModeDialect ) which extends OracleDialect and overrides the getVersion() method returing a version >= 9. ( https://hibernate.atlassian.net/browse/HHH-16034#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16034#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:b03f6a4 )

1 year, 12 months

1
0
0 / 0

[JIRA] (HHH-16034) CASE Statement in jpql throws assertion error when running H2 in Oracle mode with OracleDialect

by Marco Belladelli (JIRA)

1 year, 12 months

1
0
0 / 0

[JIRA] (HHH-15305) Update custom LIRS implementation based on BoundedConcurrentHashMap

by Sanne Grinovero (JIRA)

1 year, 12 months

1
0
0 / 0

[JIRA] (HHH-15777) wrong column type expected for audit table keys

by Pete Nattress (JIRA)

Pete Nattress ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15777 ( https://hibernate.atlassian.net/browse/HHH-15777?atlOrigin=eyJpIjoiZGQ0MW... ) Re: wrong column type expected for audit table keys ( https://hibernate.atlassian.net/browse/HHH-15777?atlOrigin=eyJpIjoiZGQ0MW... ) Hi, I’ve encountered a similar problem also doing a Spring Boot 2.7 → 3.0 upgrade. We have entities with Instant fields which are mapped to DATE columns in our Oracle DB. As of Hibernate 6 the default mapping for Instant is to TIMESTAMP WITH TIME ZONE columns, but this default can be overridden by setting hibernate.type.preferred_instant_jdbc_type=TIMESTAMP. However it appears that envers doesn’t recognise this option, and adding a @JdbcType or @JdbcTypeCode annotation explicitly on the entity fields doesn’t work either. This results in errors like this when inserting audit records: Caused by: org.hibernate.exception.GenericJDBCException: could not insert: [uk.co.mycompany.MyEntity_AUD] at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:61) at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:109) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3447) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:4058) at org.hibernate.action.internal.EntityInsertAction.execute(EntityInsertAction.java:103) at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:612) at org.hibernate.engine.spi.ActionQueue.lambda$executeActions$1(ActionQueue.java:483) at java.base/java.util.LinkedHashMap.forEach(LinkedHashMap.java:721) at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:480) at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:329) at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:39) at org.hibernate.event.service.internal.EventListenerGroupImpl.fireEventOnEachListener(EventListenerGroupImpl.java:107) at org.hibernate.internal.SessionImpl.doFlush(SessionImpl.java:1425) ... 194 common frames omitted Caused by: java.sql.SQLException: Invalid column type: 2014 at oracle.jdbc.driver.OracleStatement.getInternalType(OracleStatement.java:4369) at oracle.jdbc.driver.OraclePreparedStatement.setNullCritical(OraclePreparedStatement.java:5836) at oracle.jdbc.driver.OraclePreparedStatement.setNull(OraclePreparedStatement.java:5818) at oracle.jdbc.driver.OraclePreparedStatementWrapper.setNull(OraclePreparedStatementWrapper.java:1292) at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.setNull(HikariProxyPreparedStatement.java) at org.hibernate.type.descriptor.jdbc.BasicBinder.doBindNull(BasicBinder.java:100) at org.hibernate.type.descriptor.jdbc.BasicBinder.bind(BasicBinder.java:53) at org.hibernate.type.AbstractStandardBasicType.nullSafeSet(AbstractStandardBasicType.java:221) at org.hibernate.type.AbstractStandardBasicType.nullSafeSet(AbstractStandardBasicType.java:217) at org.hibernate.type.AbstractSingleColumnStandardBasicType.nullSafeSet(AbstractSingleColumnStandardBasicType.java:34) at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:3237) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:3420) ... 204 common frames omitted For me there’s a simple workaround of creating an AttributeConverter to explicitly define the mapping behaviour I want, which envers does pick up and apply to its generated entity definitions (you can see this in the envers HBM dump where the field type is marked as converted:: ). But I’d expect all of the type mapping logic which applies to the entity class to be applied to the audit entity in a consistent way. ( https://hibernate.atlassian.net/browse/HHH-15777#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15777#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:b03f6a4 )

1 year, 12 months

1
0
0 / 0

[JIRA] (HV-1934) Upgrade to hibernate-asciidoctor-theme 1.0.6

by Yoann Rodière (JIRA)

1 year, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4783) Run more tests for orm6/jakarta artifacts

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMzU2YThi... ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-4783?atlOrigin=eyJpIjoiMzU... ) HSEARCH-4783 ( https://hibernate.atlassian.net/browse/HSEARCH-4783?atlOrigin=eyJpIjoiMzU... ) Run more tests for orm6/jakarta artifacts ( https://hibernate.atlassian.net/browse/HSEARCH-4783?atlOrigin=eyJpIjoiMzU... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) It seems the current configuration is incorrect and leading to automatic indexing tests not being re-executed for outbox-polling coordination + when using orm6/jakarta. Also, we currently don’t run tests for orm6/jakarta artifacts against all databases. ( https://hibernate.atlassian.net/browse/HSEARCH-4783#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4783#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:b03f6a4 )

1 year, 12 months

1
0
0 / 0

[JIRA] (HSEARCH-4783) Run more tests for orm6/jakarta artifacts

by Yoann Rodière (JIRA)

1 year, 12 months

1
0
0 / 0

[JIRA] (HHH-16037) merge of a persisted entity uses an insert statement instead of an update statement resulting in duplicate entities

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDcwYjAxYzJj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiMDcwYj... ) HHH-16037 ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiMDcwYj... ) merge of a persisted entity uses an insert statement instead of an update statement resulting in duplicate entities ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiMDcwYj... ) Change By: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h2. Minimal project for reproduction * [https://github.com/lwitzani/hibernate6_singleTableIssue|https://github.co...] * project has two branches (one with hibernate 5 and one with hibernate 6) * the only difference in the branches is the updated versions of spring boot and therefore hibernate * i debugged very deep and think that it is a problem with hibernate at the location where the select statement is generated ({{LoaderSelectBuilder}}.{{createSelect}}) h2. Requisites * entity ("Person") exists that has a field which is a set of other entities ("Set \ <Leg>") * these other entities are derived from an abstract super class ("Leg extends BodyPart") * the abstract super class' inheritance strategy is SINGLE_TABLE !uml.png|width=517,height=425! h2. Reproduction * execute the test PersonPersistenceTest.shouldUseSQLUpdateToChangeThePersonName * the test basically ** creates a Person (without Legs) and saves it using the repository ** refetches the Person by findById ** changes the Person's name ** saves the changed Person again h2. Observations in Hibernate 5.6.14.Final * when the second save is called (after changing the name) there will be a select statement which is used to check if the entity already exists ** the body_part table is joined via left outer join ** the where clause here only consists of "where [person.id|http://person.id] = <id>" * the entity is correctly found by the select statement so afterwards an update statement follows * result: one entity exists (the changed one) !hibernate5.png|width=1265,height=692! h2. Observations in Hibernate 6.1.6.Final * when the second save is called (after changing the name) there will be a different select statement now ** the body_part table is joined via left join now (not outer) ** the critical change here is that the where clause now suddenly consists of "where body_part.discriminator = 'LegBodyPart' and [person.id|http://person.id] = <id>" * although the entity exists, it is not found by the select statement so afterwards an insert statement follows which creates a second Person with a new id * result: two entities exist (the original one and the changed one) !hibernate6.png|width=1179,height=644! h1. Summary * after updating spring boot to 3.0.1 which also updates hibernate to 6.1.6.Final it does not seem to be possible to update an entity with this constellation * the main difference is that an additional and unexpected where clause is added which prevents finding the correct entity in this case * the result is that a new entity is persisted instead of the existing one being updated ( https://hibernate.atlassian.net/browse/HHH-16037#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16037#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:b03f6a4 )

1 year, 12 months

1
0
0 / 0

[JIRA] (HHH-16037) merge of a persisted entity uses an insert statement instead of an update statement resulting in duplicate entities

by Lukas Witzani (JIRA)

Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTczOWI3MTE1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiNTczOW... ) HHH-16037 ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiNTczOW... ) merge of a persisted entity uses an insert statement instead of an update statement resulting in duplicate entities ( https://hibernate.atlassian.net/browse/HHH-16037?atlOrigin=eyJpIjoiNTczOW... ) Change By: Lukas Witzani ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) h2. Minimal project for reproduction * [https://github.com/lwitzani/hibernate6_singleTableIssue|https://github.co...] * project has two branches (one with hibernate 5 and one with hibernate 6) * the only difference in the branches is the updated versions of spring boot and therefore hibernate * i debugged very deep and think that it is a problem with hibernate at the location where the select statement is generated ({{LoaderSelectBuilder}}.{{createSelect}}) h2. Requisites * entity ("Person") exists that has a field which is a set of other entities ("Set\<Leg>") * these other entities are derived from an abstract super class ("Leg extends BodyPart") * the abstract super class' inheritance strategy is SINGLE_TABLE !uml.png|width=517,height=425! h2. Reproduction * execute the test PersonPersistenceTest.shouldUseSQLUpdateToChangeThePersonName * the test basically ** creates a Person (without Legs) and saves it using the repository ** refetches the Person by findById ** changes the Person's name ** saves the changed Person again h2. Observations in Hibernate 5.6.14.Final * when the second save is called (after changing the name) there will be a select statement which is used to check if the entity already exists ** the body_part table is joined via left outer join ** the where clause here only consists of "where [person.id|http://person.id] = \ <id>" * the entity is correctly found by the select statement so afterwards an update statement follows * result: one entity exists (the changed one) !hibernate5.png|width=1265,height=692! h2. Observations in Hibernate 6.1.6.Final * when the second save is called (after changing the name) there will be a different select statement now ** the body_part table is joined via left join now (not outer) ** the critical change here is that the where clause now suddenly consists of "where body_part.discriminator = 'LegBodyPart' and [person.id|http://person.id] = \ <id>" * although the entity exists, it is not found by the select statement so afterwards an insert statement follows which creates a second Person with a new id * result: two entities exist (the original one and the changed one) !hibernate6.png|width=1179,height=644! h1. Summary * after updating spring boot to 3.0.1 which also updates hibernate to 6.1.6.Final it does not seem to be possible to update an entity with this constellation * the main difference is that an additional and unexpected where clause is added which prevents finding the correct entity in this case * the result is that a new entity is persisted instead of the existing one being updated ( https://hibernate.atlassian.net/browse/HHH-16037#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16037#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:b03f6a4 )

1 year, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2023