October 2018 - hibernate-dev - Jboss List Archives

by Guillaume Smet

Hi everyone, Here are the minutes of this week's meeting: 15:42 < jbott> Meeting ended Tue Oct 9 13:42:30 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 15:42 < jbott> Minutes: http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/... 15:42 < jbott> Minutes (text): http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/... 15:42 < jbott> Log: http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2018/... Cheers, -- Guillaume

7 years, 1 month

1
0
0 / 0

*-to-one associations and @NotFound

by Gail Badner

As a result of fixing HHH-12436 <https://hibernate.atlassian.net/browse/HHH-12436>, some eager *-to-one associations that were loaded using FetchMode.JOIN may instead be loaded using FetchMode.SELECT, and vice-versa. In some cases, @NotFound behavior is different depending on the FetchMode for the association. The reason why FetchMode may change due to HHH-12436 <https://hibernate.atlassian.net/browse/HHH-12436> is that the ForeignKeyDirection of some *-to-one associations were incorrect. Correcting the ForeignKeyDirection will result in a different AssociationKey, which may ultimately affect the FetchMode Hibernate assigns to an association. My hope is to resolve the inconsistencies before fixing HHH-12436 <https://hibernate.atlassian.net/browse/HHH-12436>, so it does not result in a change in application behavior. I've created a Google Doc to document the inconsistencies and to make it easier to discuss how to go about resolving them: https://docs.google.com/document/d/1o3Q6tYD5jjxC6Ok7vBYzxRGsixpG46p-5zDiD... Please feel free to request access to the document if you wish to review or add comments. Regards, Gail

7 years, 1 month

1
2
0 / 0

What should happen to queued operations when a collection is detached?

by Gail Badner

HHH-11209 involves a bug merging a detached entity with an uninitialized collection that has queued operations. After looking into this issue I found a bug where AbstractPersistentCollection#operationQueue was not being cleared after a commit, if there was no cascade mapped for the collection. I've fixed that in a PR. [1] After that fix, the detached entity in the test case attached to HHH-11209 has an uninitialized entity without any queued operations after commit, which can be merged successfully in a new session/transaction. There is still a problem when Hibernate tries to merge a detached entity has an uninitialized collection with queued operations though. My PR throws UnsupportedOperationException in this case, and there is a test case that reproduces it. I've been working on a fix to add support for this, but I have my doubts that it really should be supported. I see that prior to fixing HHH-5855 (which caused HHH-11209), Hibernate simply ignored the queued operations in the detached collection. [2]. The fix for HHH-5855 properly dealt with merging a managed collection that was uninitialized with queued operations. It introduced the bug where a NullPointerException would get thrown if that collection was detached. If we want to support merging the queued operations, then I would consider that an improvement. Would this be a worthwhile improvement? I'm guessing not, but I wanted to get some opinions. For now, I see a couple of ways to deal with this so that HHH-11209 can be wrapped up: 1) ignore queued operations in a detached collection when merging, as was done before HHH-5855 was fixed. 2) clear the queued operations when the collection is detached. Comments? Thanks, Gail [1] https://github.com/hibernate/hibernate-orm/pull/2460 [2] https://github.com/hibernate/hibernate-orm/commit/c1934b72edb4f7815209376...

7 years, 1 month

2
4
0 / 0

Legacy Jenkins API tokens

by Yoann Rodiere

Hello, FYI, I just revoked all the legacy Jenkins API tokens, as recommended. Don't worry, I'm talking about tokens issued by Jenkins to each user and allowing to use Jenkins APIs; this is completely unrelated to GitHub/AWS credentials and such. More information: https://jenkins.io/blog/2018/07/02/new-api-token-system/ Apparently the tokens weren't being used by anyone, or at least haven't been for a few weeks. But if you did need it, I guess you can always follow the link above to find out how to use a new token. Cheers, Yoann Rodière Hibernate NoORM Team yoann(a)hibernate.org

7 years, 1 month

1
0
0 / 0

Should the LocalTimeType use the globally configured TimeZone?

by Vlad Mihalcea

Hi, While reviewing this Jira issue: https://hibernate.atlassian.net/browse/HHH-12988 and further discussing it via Twitter, I wonder if we should persist LocalTime as-is without any TimeZone transformation that may be done if we enable `hibernate.jdbc.time_zone`? According to the Date/Time API, LocalTime should not be relative to any TimeZone. If we make this change, it means we need to use a LocalTime SQL descriptor that ignores the jdbc.time_zone property, and the change is going to break compatibility as well. Vlad

7 years, 1 month

6
9
0 / 0

StatelessSession and JTA platform without transaction manager

by Guillaume Smet

Hi, I'm triaging the latest issues and I stumbled upon this one: https://hibernate.atlassian.net/browse/HHH-13002 . This particular issue happens because our OSGi stuff enforce an OsgiJtaPlatform even if there is no JTA transaction manager. I'm not very familiar with JTA in ORM but I find suspicious that StatelessSession doesn't check somehow that a JTA transaction manager is in motion before checking things with it namely here: https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src... In SessionFactoryImpl, we somehow check that the JTA transaction manager is OK here: https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src... I suppose that's why standard sessions are not affected. Not sure what the right fix would be so I thought I might as well ask. Thanks for any insights. -- Guillaume

7 years, 1 month

1
0
0 / 0

Hibernate OGM 5.4.0.CR1 is out

by Fabio Massimo Ercoli

Hibernate OGM 5.4.0.CR1 is ready! Some improvement was the support of Infinispan remote transactions over HotRod client, java.time field types and MongoDB ReadConcern strategy. All the details in the blog post: http://in.relation.to/2018/10/01/hibernate-ogm-5-4-CR1-released/ Thanks, Fabio

7 years, 1 month

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-dev October 2018