June 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-14055) Allow java.util.UUID as type of field annotated with @RevisionNumber

by Borislav Banchev (JIRA)

Borislav Banchev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ed6071... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTI3ZjRiNTQ1... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-14055?atlOrigin=eyJpIjoiNTI3Zj... ) HHH-14055 ( https://hibernate.atlassian.net/browse/HHH-14055?atlOrigin=eyJpIjoiNTI3Zj... ) Allow java.util.UUID as type of field annotated with @RevisionNumber ( https://hibernate.atlassian.net/browse/HHH-14055?atlOrigin=eyJpIjoiNTI3Zj... ) Change By: Borislav Banchev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ed6071... ) Currently _The field annotated with @RevisionNumber must be of type int, Integer, long, Long _ Long_ and this is a major constraint in specific cases and it is a known [issue|https://stackoverflow.com/questions/43465734/issue-with-implementin...]. Allowing a user to chose UUID as a field type will give extra flexibility. The proposed change is in RevisionInfoConfiguration class. ( https://hibernate.atlassian.net/browse/HHH-14055#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14055#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#100127- sha1:2783216 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14055) Allow java.util.UUID as type of field annotated with @RevisionNumber

by Borislav Banchev (JIRA)

Borislav Banchev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ed6071... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYTEzMTNiODU4... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-14055?atlOrigin=eyJpIjoiYTEzMT... ) HHH-14055 ( https://hibernate.atlassian.net/browse/HHH-14055?atlOrigin=eyJpIjoiYTEzMT... ) Allow java.util.UUID as type of field annotated with @RevisionNumber ( https://hibernate.atlassian.net/browse/HHH-14055?atlOrigin=eyJpIjoiYTEzMT... ) Issue Type: New Feature Affects Versions: 5.0.12 Assignee: Chris Cranford ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-envers Created: 02/Jun/2020 01:20 AM Priority: Major Reporter: Borislav Banchev ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ed6071... ) Currently _The field annotated with @RevisionNumber must be of type int, Integer, long, Long _ and this is a major constraint in specific cases and it is a known issue ( https://stackoverflow.com/questions/43465734/issue-with-implementing-uuid... ). Allowing a user to chose UUID as a field type will give extra flexibility. The proposed change is in RevisionInfoConfiguration class. ( https://hibernate.atlassian.net/browse/HHH-14055#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14055#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#100127- sha1:2783216 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14054) Hibernate insert/update ordering wrt unique constraints

by Koen Serneels (JIRA)

Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMGE3OTFhMWVj... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiMGE3OT... ) HHH-14054 ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiMGE3OT... ) Hibernate insert/update ordering wrt unique constraints ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiMGE3OT... ) Change By: Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hi. In the example created for this issue (please see: [https://github.com/koen-serneels/hibernate-uc-violation|https://github.co...]) is an entity with a single property ‘value’ and unique constraint. Initially there is an existing instance with it’s property ‘value’ equal to ‘val1’. When we now do following within the same transaction: * change the value on the existing entity from “val1” to “val2” * add a new entity with “val1” We get a ConstraintViolationException because Hibernate is executing the insert before the update. Now, is this actually expected knowing that Hibernate knows about the unique constraint and that it would make more sense to perform the insert after the update or is this a bug /missing feature ? Btw; I posted this first on the forum ([https://discourse.hibernate.org/t/hibernate-insert-update-ordering-wrt-un...]), but in absence of any response I started thinking this might be a bug/feature. Thanks\! ( https://hibernate.atlassian.net/browse/HHH-14054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14054#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#100127- sha1:2783216 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14054) Hibernate insert/update ordering wrt unique constraints

by Koen Serneels (JIRA)

Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNjE4NGM0YTQ2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNjE4NG... ) HHH-14054 ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNjE4NG... ) Hibernate insert/update ordering wrt unique constraints ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNjE4NG... ) Change By: Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hi. In the example created for this issue (please see: [https://github.com/koen-serneels/hibernate-uc-violation|https://github.co...]) is an entity with a single property ‘value’ and unique constraint. Initially there is an existing instance with it’s property ‘value’ equal to ‘val1’. When we now do following within the same transaction: * change the value on the existing entity from “val1” to “val2” * add a new entity with “val1” We get a ConstraintViolationException because Hibernate is executing the insert before the update. Now, is this actually expected knowing that Hibernate knows about the unique constraint and that it would make more sense to perform the insert after the update or is this a bug? Btw; I posted this first on the forum ([https://discourse.hibernate.org/t/hibernate-insert-update-ordering-wrt-un...] ) , but in absence of any response I started thinking this might be a bug/feature. Thanks\! ( https://hibernate.atlassian.net/browse/HHH-14054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14054#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#100127- sha1:2783216 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14054) Hibernate insert/update ordering wrt unique constraints

by Koen Serneels (JIRA)

Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNDliZTJmNGE5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNDliZT... ) HHH-14054 ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNDliZT... ) Hibernate insert/update ordering wrt unique constraints ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNDliZT... ) Change By: Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hi. In the example created for this issue (please see: [https://github.com/koen-serneels/hibernate-uc-violation|https://github.co...]) is an entity with a single property ‘value’ and unique constraint. Initially there is an existing instance with it’s property ‘value’ equal to ‘val1’. When we now do following within the same transaction: * change the value on the existing entity from “val1” to “val2” * add a new entity with “val1” We get a ConstraintViolationException because Hibernate is executing the insert before the update. Now ; * Is , is this actually expected knowing that Hibernate knows about the unique constraint and that it would make more sense to perform the insert after the update ? * Is there a more elegant way to deal with or is this than performing manual flushes as illustrated by the test case a bug ? Btw; I posted this first on the forum ([https://discourse.hibernate.org/t/hibernate-insert-update-ordering-wrt-un...], but in absence of any response I started thinking this might be a bug/feature. Thanks\! ( https://hibernate.atlassian.net/browse/HHH-14054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14054#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#100127- sha1:6728f9f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14054) Hibernate insert/update ordering wrt unique constraints

by Koen Serneels (JIRA)

Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOWMwMTMyNjg1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiOWMwMT... ) HHH-14054 ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiOWMwMT... ) Hibernate insert/update ordering wrt unique constraints ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiOWMwMT... ) Change By: Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hi. In the example created for this issue (please see: [https://github.com/koen-serneels/hibernate-uc-violation|https://github.co...]) is an entity with a single property ‘value’ and unique constraint. Initially there is an existing instance with it’s property ‘value’ equal to ‘val1’. When we now do following within the same transaction: * change the value on the existing entity from “val1” to “val2” * add a new entity with “val1” We get a ConstraintViolationException because Hibernate is executing the insert before the update. Two questions about this behavior Now; * Is this actually expected knowing that Hibernate knows about the unique constraint and that it would make more sense to perform the insert after the update? * Is there a more elegant way to deal with this than performing manual flushes as illustrated by the test case? Btw; I posted this first on the forum ([https://discourse.hibernate.org/t/hibernate-insert-update-ordering-wrt-un...], but in absence of any response I started thinking this might be a bug/feature. Thanks\! ( https://hibernate.atlassian.net/browse/HHH-14054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14054#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#100127- sha1:2783216 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14054) Hibernate insert/update ordering wrt unique constraints

by Koen Serneels (JIRA)

Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNzhiMTVlYmVl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNzhiMT... ) HHH-14054 ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNzhiMT... ) Hibernate insert/update ordering wrt unique constraints ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNzhiMT... ) Change By: Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hi. In the example created for this question issue (please see: [https://github.com/koen-serneels/hibernate-uc-violation|https://github.co...]) is an entity with a single property ‘value’ and unique constraint. Initially there is an existing instance with it’s property ‘value’ equal to ‘val1’. When we now do following within the same transaction: * change the value on the existing entity from “val1” to “val2” * add a new entity with “val1” We get a ConstraintViolationException because Hibernate is executing the insert before the update. Two questions about this behavior * Is this actually expected knowing that Hibernate knows about the unique constraint and that it would make more sense to perform the insert after the update? * Is there a more elegant way to deal with this than performing manual flushes as illustrated by the test case? Btw; I posted this first on the forum ([https://discourse.hibernate.org/t/hibernate-insert-update-ordering-wrt-un...], but in absence of any response I started thinking this might be a bug/feature. Thanks\! ( https://hibernate.atlassian.net/browse/HHH-14054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14054#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#100127- sha1:6728f9f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14054) Hibernate insert/update ordering wrt unique constraints

by Koen Serneels (JIRA)

Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNThkNTMxM2Uy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNThkNT... ) HHH-14054 ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNThkNT... ) Hibernate insert/update ordering wrt unique constraints ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiNThkNT... ) Change By: Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hi. In the example created for this question (please see: [https://github.com/koen-serneels/hibernate-uc-violation|https://github.co...]) is an entity with a single property ‘value’ and unique constraint. Initially there is an existing instance with it’s property ‘value’ equal to ‘val1’. When we now do following within the same transaction: * change the value on the existing entity from “val1” to “val2” * add a new entity with “val1” We get a ConstraintViolationException because Hibernate is executing the insert before the update. Two questions about this behavior * Is this actually expected knowing that Hibernate knows about the unique constraint and that it would make more sense to perform the insert after the update? * Is there a more elegant way to deal with this than performing manual flushes as illustrated by the test case? Btw; I posted this first on the forum ([https://discourse.hibernate.org/t/hibernate-insert-update-ordering-wrt-un...], but in absence of any response I started thinking this might be a bug /feature. Thanks \ ! ( https://hibernate.atlassian.net/browse/HHH-14054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14054#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#100127- sha1:2783216 )

3 years, 11 months

1
0
0 / 0

[JIRA] (HHH-14054) Hibernate insert/update ordering wrt unique constraints

by Koen Serneels (JIRA)

Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjhjYzllNTRm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiYjhjYz... ) HHH-14054 ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiYjhjYz... ) Hibernate insert/update ordering wrt unique constraints ( https://hibernate.atlassian.net/browse/HHH-14054?atlOrigin=eyJpIjoiYjhjYz... ) Issue Type: Bug Affects Versions: 5.4.17 Assignee: Unassigned Components: hibernate-core Created: 02/Jun/2020 00:05 AM Priority: Major Reporter: Koen Serneels ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hi. In the example created for this question (please see: https://github.com/koen-serneels/hibernate-uc-violation ) is an entity with a single property ‘value’ and unique constraint. Initially there is an existing instance with it’s property ‘value’ equal to ‘val1’. When we now do following within the same transaction: * change the value on the existing entity from “val1” to “val2” * add a new entity with “val1” We get a ConstraintViolationException because Hibernate is executing the insert before the update. Two questions about this behavior * Is this actually expected knowing that Hibernate knows about the unique constraint and that it would make more sense to perform the insert after the update? * Is there a more elegant way to deal with this than performing manual flushes as illustrated by the test case? Btw; I posted this first on the forum ( https://discourse.hibernate.org/t/hibernate-insert-update-ordering-wrt-un... , but in absence of any response I started thinking this might be a bug. Thanks! ( https://hibernate.atlassian.net/browse/HHH-14054#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14054#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#100127- sha1:6728f9f )

3 years, 11 months

1
0
0 / 0

[JIRA] (HBX-2037) Replace readme.txt by README.md in 'test/oracle'

by Koen Aers (JIRA)

3 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2020