March 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16343) Batch Fetch Size + PreLoadEventListener + Polymorphic Entity with cache enabled could lead to IllegalStateException: Illegal pop() with non-matching JdbcValuesSourceProcessingState

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16343 ( https://hibernate.atlassian.net/browse/HHH-16343?atlOrigin=eyJpIjoiMTExMW... ) Re: Batch Fetch Size + PreLoadEventListener + Polymorphic Entity with cache enabled could lead to IllegalStateException: Illegal pop() with non-matching JdbcValuesSourceProcessingState ( https://hibernate.atlassian.net/browse/HHH-16343?atlOrigin=eyJpIjoiMTExMW... ) No, the pre-load would not be called again when initializing a proxy. In fact, using *pre* -load to capture the loaded state is not correct, the entity will never be “loaded” at this point since this event is called before (pre) loading. For that purpose I’d suggest using Hibernate’s PostLoadEvent or even the @PostLoad JPA lifecycle callback ( https://jakarta.ee/specifications/persistence/3.1/jakarta-persistence-spe... ) method annotation on the entity class itself. ( https://hibernate.atlassian.net/browse/HHH-16343#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16343#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16343) Batch Fetch Size + PreLoadEventListener + Polymorphic Entity with cache enabled could lead to IllegalStateException: Illegal pop() with non-matching JdbcValuesSourceProcessingState

by Jones (JIRA)

Jones ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16343 ( https://hibernate.atlassian.net/browse/HHH-16343?atlOrigin=eyJpIjoiZTAzZW... ) Re: Batch Fetch Size + PreLoadEventListener + Polymorphic Entity with cache enabled could lead to IllegalStateException: Illegal pop() with non-matching JdbcValuesSourceProcessingState ( https://hibernate.atlassian.net/browse/HHH-16343?atlOrigin=eyJpIjoiZTAzZW... ) Thanks. I’m using the PreLoadEventListener to capture the loaded state. I could ignore the non initialized proxy entities, but my question is: when this proxy is initialized, would it then call the preload listener again with the loaded state? Because I just want to guarantee that I capture the loaded state when it gets loaded. ( https://hibernate.atlassian.net/browse/HHH-16343#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16343#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16369) PostGIS function st_extent(geometry) does not work

by Marco Zühlke (JIRA)

Marco Zühlke ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61f9220... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzYzY2UzNDRi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16369?atlOrigin=eyJpIjoiYzYzY2... ) HHH-16369 ( https://hibernate.atlassian.net/browse/HHH-16369?atlOrigin=eyJpIjoiYzYzY2... ) PostGIS function st_extent(geometry) does not work ( https://hibernate.atlassian.net/browse/HHH-16369?atlOrigin=eyJpIjoiYzYzY2... ) Change By: Marco Zühlke ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61f9220... ) I'm troubleshooting with an issue when using PostGIS function st_extent. Entity/Repository: {code:java}@Entity @Table(name = "geometry_entity") @Data public class GeometryEntity { @Id @GeneratedValue(generator = "system-uuid") @GenericGenerator(name = "system-uuid", strategy = "org.hibernate.id.UUIDGenerator") private UUID id; @Column(name = "the_geom") private Polygon geometry; } public interface GeometryEntityRepository extends CrudRepository<GeometryEntity, UUID> { @Query(value = "select extent(geometry) from GeometryEntity") Optional<Polygon> getExtentByHQLQuery getExtentByJPQL (); @Query(value = "select st_extent(geometry) from GeometryEntity") Optional<Polygon> getExtentByST_PrefixedFunctionName(); @Query(value = "select st_extent(the_geom) from geometry_entity", nativeQuery = true) Optional<Polygon> getExtentByNativeQuery(); }{code} According to the doc [https://docs.jboss.org/hibernate/orm/6.1/userguide/html_single/Hibernate_... extent AND st_extent should work. I have three different queries, two of them are using HQL JPQL , the other one is written native. None of them work, all results in an error. The attempt to call {{getExtentByHQLQuery}}() results in: {noformat}2023-03-24T17:19:37.115+01:00 ERROR 456308 --- [ main] o.h.engine.jdbc.spi.SqlExceptionHelper : ERROR: function extent(geometry) does not exist Hinweis: No function matches the given name and argument types. You might need to add explicit type casts. Position: 8 org.springframework.dao.InvalidDataAccessResourceUsageException: JDBC exception executing SQL [select extent(g1_0.the_geom) from field g1_0]; SQL [n/a]{noformat} The attempt to call {{getExtentByST_PrefixedFunctionName}}() and {{getExtentByNativeQuery()}}results in: {noformat}org.springframework.core.convert.ConverterNotFoundException: No converter found capable of converting from type [org.springframework.data.jpa.repository.query.AbstractJpaQuery$TupleConverter$TupleBackedMap] to type [org.locationtech.jts.geom.Polygon] at org.springframework.core.convert.support.GenericConversionService.handleConverterNotFound(GenericConversionService.java:322){noformat} Just as a side note, using st_envelope instead of st_extent works on HQL JPQL queries, using a native query ends up with same {{ConverterNotFoundException}} I get by using st_extent. * spring-boot:3.0.4 * hibernate-spatial:6.1.7 * postgres/postgis:15-3.3 Test case to reproduce the error: [https://github.com/marcozet/spring-boot-3-hibernate-spatial|https://githu...] ( https://hibernate.atlassian.net/browse/HHH-16369#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16369#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16380) Avoid map-based mapping metamodel access when instantiating entity instances

by Marco Belladelli (JIRA)

3 years

1
0
0 / 0

[JIRA] (HHH-16380) Avoid map-based mapping metamodel access when instantiating entity instances

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjBhNjZkMWQw... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16380?atlOrigin=eyJpIjoiZjBhNj... ) HHH-16380 ( https://hibernate.atlassian.net/browse/HHH-16380?atlOrigin=eyJpIjoiZjBhNj... ) Avoid map-based mapping metamodel access when instantiating entity instances ( https://hibernate.atlassian.net/browse/HHH-16380?atlOrigin=eyJpIjoiZjBhNj... ) Issue Type: Improvement Assignee: Unassigned Created: 27/Mar/2023 03:58 AM Priority: Major Reporter: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) We can avoid accessing the mapping metamodel’s entity persister map by entity name when instantiating entities since we already have the concrete EntityPersister , see AbstractEntityInitializer#instantiateEntity. ( https://hibernate.atlassian.net/browse/HHH-16380#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16380#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16369) PostGIS function st_extent(geometry) does not work

by Marco Zühlke (JIRA)

Marco Zühlke ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61f9220... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMGUzYjY0Nzgw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16369?atlOrigin=eyJpIjoiMGUzYj... ) HHH-16369 ( https://hibernate.atlassian.net/browse/HHH-16369?atlOrigin=eyJpIjoiMGUzYj... ) PostGIS function st_extent(geometry) does not work ( https://hibernate.atlassian.net/browse/HHH-16369?atlOrigin=eyJpIjoiMGUzYj... ) Change By: Marco Zühlke ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=61f9220... ) I'm troubleshooting with an issue when using PostGIS function st_extent. Entity/Repository: {code:java}@Entity @Table(name = "geometry_entity") @Data public class GeometryEntity { @Id @GeneratedValue(generator = "system-uuid") @GenericGenerator(name = "system-uuid", strategy = "org.hibernate.id.UUIDGenerator") private UUID id; @Column(name = "the_geom") private Polygon geometry; } public interface GeometryEntityRepository extends CrudRepository<GeometryEntity, UUID> { @Query(value = "select extent(geometry) from GeometryEntity") Optional<Polygon> getExtentByHQLQuery(); @Query(value = "select st_extent(geometry) from GeometryEntity") Optional<Polygon> getExtentByST_PrefixedFunctionName(); @Query(value = "select st_extent(the_geom) from geometry_entity", nativeQuery = true) Optional<Polygon> getExtentByNativeQuery(); }{code} According to the doc [https://docs.jboss.org/hibernate/orm/6.1/userguide/html_single/Hibernate_... extent AND st_extent should work. I have three different queries, two of them are using HQL, the other one is written native. None of them work, all results in an error. The attempt to call {{getExtentByHQLQuery}}() results in: {noformat}2023-03-24T17:19:37.115+01:00 ERROR 456308 --- [ main] o.h.engine.jdbc.spi.SqlExceptionHelper : ERROR: function extent(geometry) does not exist Hinweis: No function matches the given name and argument types. You might need to add explicit type casts. Position: 8 org.springframework.dao.InvalidDataAccessResourceUsageException: JDBC exception executing SQL [select extent(g1_0.the_geom) from field g1_0]; SQL [n/a]{noformat} The attempt to call {{getExtentByST_PrefixedFunctionName}}() and {{getExtentByNativeQuery()}}results in: {noformat}org.springframework.core.convert.ConverterNotFoundException: No converter found capable of converting from type [org.springframework.data.jpa.repository.query.AbstractJpaQuery$TupleConverter$TupleBackedMap] to type [org.locationtech.jts.geom.Polygon] at org.springframework.core.convert.support.GenericConversionService.handleConverterNotFound(GenericConversionService.java:322){noformat} Just as a side note, using st_envelope instead of st_extent works on HQL queries, using a native query ends up with same {{ConverterNotFoundException}} I get by using st_extent. * spring-boot:3.0.4 * hibernate-spatial:6.1.7 * postgres/postgis:15-3.3 Simple app Test case to reproduce the error: [https://github.com/marcozet/spring-boot-3-hibernate-spatial|https://githu...] ( https://hibernate.atlassian.net/browse/HHH-16369#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16369#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16379) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement

by Holger Bach (JIRA)

Holger Bach ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=642158a... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYmEzMDcwMzUw... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiYmEzMD... ) HHH-16379 ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiYmEzMD... ) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiYmEzMD... ) Change By: Holger Bach ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=642158a... ) When updating an derived entity containing several field, not all changed fields will be updated Having a base entity containing two fields named *checksum* and *variantName* and a derived entity containing one field named *fileSize*. Create an database entry, {noformat}FileVersion version = new FileVersion(); version.setId("1"); version.setFileSize(100L); version.setCheckSumMD5("ABCDEF"); version.setVariantName("A");{noformat} change all fields of the existing database entry (see testcase *testWithDynamicUpdate*) {noformat}version.setCheckSumMD5("XXXXXXXX"); version.setVariantName("B"); version.setFileSize(200L);{noformat} The following update statement will be created {noformat}Hibernate: update Versionen set CHECKSUM=?, FILESIZE=? where VERS_NUMMER=?{noformat} Only *checksum* and *fileSize* will be updated, but not the field *variantName*. Problem occurs in file *AbstractEntityPersister* in function *resolveDirtyAttributeIndexes*. The dirty fields will be sorted bei name {noformat}Arrays.sort( attributeNames ); attributeName = {checkSum, fileSize, variantName}{noformat} In the for loop the fields in *attributeNames* will be compared to the array *attributeMappings*, which contains the mapping informations according to the annotations. *attributeMappings* has the following order: {noformat}attributeMappings = { AbstarctVersion AbstractVersion.checksum, AbstractVersion.variantName, FileVersion.fileSize}{noformat} The for loop does only recognize the fields *checksum* and *fileSize. variantName* will not be processed. A sample project with test case can be found [here|https://github.com/HoBa1975/hibernate-mapping] ( https://hibernate.atlassian.net/browse/HHH-16379#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16379#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16379) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement

by Holger Bach (JIRA)

Holger Bach ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=642158a... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiN2VkMmYzMDc5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiN2VkMm... ) HHH-16379 ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiN2VkMm... ) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiN2VkMm... ) Change By: Holger Bach ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=642158a... ) When updating an derived entity containing several field, not all changed fields will be updated Having a base entity containing two fields named *checksum* and *variantName* and a derived entity containing one field named *fileSize*. Create an database entry, {noformat}FileVersion version = new FileVersion(); version.setId("1"); version.setFileSize(100L); version.setCheckSumMD5("ABCDEF"); version.setVariantName("A");{noformat} change all fields of the existing database entry (see testcase *testWithDynamicUpdate*) {noformat}version.setCheckSumMD5("XXXXXXXX"); version.setVariantName("B"); version.setFileSize(200L);{noformat} The following update statement will be created {noformat}Hibernate: update Versionen set CHECKSUM=?, FILESIZE=? where VERS_NUMMER=?{noformat} Only *checksum* and *fileSize* will be updated, but not the field *variantName*. Problem occurs in file *AbstractEntityPersister* in function *resolveDirtyAttributeIndexes*. ch The dirty fields will be sorted bei name {noformat}Arrays.sort( attributeNames ); attributeName = {checkSum, fileSize, variantName}{noformat} In the for loop the fields in *attributeNames* will be compared to the array *attributeMappings*, which contains the mapping informations according to the annotations. *attributeMappings* has the following order: {noformat}attributeMappings = {AbstarctVersion.checksum, AbstractVersion.variantName, FileVersion.fileSize}{noformat} The for loop does only recognize the fields *checksum* and *fileSize. variantName* will not be processed. A sample project with test case can be found [here|https://github.com/HoBa1975/hibernate-mapping] ( https://hibernate.atlassian.net/browse/HHH-16379#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16379#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16379) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement

by Holger Bach (JIRA)

Holger Bach ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=642158a... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjhlNWZiMmY2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiMjhlNW... ) HHH-16379 ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiMjhlNW... ) @DynamicUpdate and 'enableDirtyTracking=true' leads to wrong update statement ( https://hibernate.atlassian.net/browse/HHH-16379?atlOrigin=eyJpIjoiMjhlNW... ) Issue Type: Bug Affects Versions: 6.0.2, 6.1.7 Assignee: Unassigned Components: hibernate-orm-modules Created: 27/Mar/2023 03:28 AM Environment: Java 17 Priority: Major Reporter: Holger Bach ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=642158a... ) When updating an derived entity containing several field, not all changed fields will be updated Having a base entity containing two fields named *checksum* and *variantName* and a derived entity containing one field named *fileSize*. Create an database entry, FileVersion version = new FileVersion(); version.setId("1"); version.setFileSize(100L); version.setCheckSumMD5("ABCDEF"); version.setVariantName("A"); change all fields of the existing database entry (see testcase *testWithDynamicUpdate* ) version.setCheckSumMD5("XXXXXXXX"); version.setVariantName("B"); version.setFileSize(200L); The following update statement will be created Hibernate: update Versionen set CHECKSUM=?, FILESIZE=? where VERS_NUMMER=? Only *checksum* and *fileSize* will be updated, but not the field *variantName*. Problem occurs in file *AbstractEntityPersister* in function *resolveDirtyAttributeIndexes*. ch The dirty fields will be sorted bei name Arrays.sort( attributeNames ); attributeName = {checkSum, fileSize, variantName} In the for loop the fields in *attributeNames* will be compared to the array *attributeMappings* , which contains the mapping informations according to the annotations. *attributeMappings* has the following order: attributeMappings = {AbstarctVersion.checksum, AbstractVersion.variantName, FileVersion.fileSize} The for loop does only recognize the fields *checksum* and *fileSize. variantName* will not be processed. A sample project with test case can be found here ( https://github.com/HoBa1975/hibernate-mapping ) ( https://hibernate.atlassian.net/browse/HHH-16379#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16379#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

[JIRA] (HHH-16378) SQM fails to resolve target type of association defined in mappersuperclass with generics

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16378 ( https://hibernate.atlassian.net/browse/HHH-16378?atlOrigin=eyJpIjoiNDc0YW... ) Re: SQM fails to resolve target type of association defined in mappersuperclass with generics ( https://hibernate.atlassian.net/browse/HHH-16378?atlOrigin=eyJpIjoiNDc0YW... ) Here’s a reproducer: https://github.com/hibernate/hibernate-orm/pull/6296 ( https://github.com/hibernate/hibernate-orm/pull/6296 ) And the same on 5.6 (doesn’t fail): https://github.com/hibernate/hibernate-orm/pull/6297 ( https://github.com/hibernate/hibernate-orm/pull/6297 ) ( https://hibernate.atlassian.net/browse/HHH-16378#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16378#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#100219- sha1:ac3e918 )

3 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2023