July 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-13926) StaleStateException message should not contain SQL parameters

by Mickaël TRICOT (JIRA)

5 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13926) StaleStateException should (optionally) not leak statements in the logs

by Mickaël TRICOT (JIRA)

Mickaël TRICOT ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13926 ( https://hibernate.atlassian.net/browse/HHH-13926?atlOrigin=eyJpIjoiOTc2Mj... ) Re: StaleStateException should (optionally) not leak statements in the logs ( https://hibernate.atlassian.net/browse/HHH-13926?atlOrigin=eyJpIjoiOTc2Mj... ) I agree. Having the parameters logged somehow could be helpful but they probably should not be there by default. I’ll rework this issue. ( https://hibernate.atlassian.net/browse/HHH-13926#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13926#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#100133- sha1:bf400b0 )

5 years, 5 months

1
0
0 / 0

[JIRA] (HHH-13926) StaleStateException should (optionally) not leak statements in the logs

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13926 ( https://hibernate.atlassian.net/browse/HHH-13926?atlOrigin=eyJpIjoiYmYxZD... ) Re: StaleStateException should (optionally) not leak statements in the logs ( https://hibernate.atlassian.net/browse/HHH-13926?atlOrigin=eyJpIjoiYmYxZD... ) Thanks yes then I agree, we shouldn’t log the parameters. Looks like this was introduced as https://hibernate.atlassian.net/browse/HHH-12878. I don’t think this should be based on the show_sql property though, that’s meant for a different aspect and it would be confusing to have it interact with this aspect. I actually think we should never log parameters in the stacktrace of a {{StaleStateException}}so we could keep it simple and avoid any configuration property? ( https://hibernate.atlassian.net/browse/HHH-13926#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13926#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#100133- sha1:bf400b0 )

5 years, 5 months

1
0
0 / 0

[JIRA] (WEBSITE-591) Broken link: http://hibernate.org/dtd/hibernate-configuration-5.2.0.dtd

by Yoann Rodière (JIRA)

5 years, 5 months

1
0
0 / 0

[JIRA] (HHH-14102) orphanRemoval behaviour differ from lazy to eager loading

by Florian Kern (JIRA)

Florian Kern ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ee102c... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZWI1ZjE5MzBl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14102?atlOrigin=eyJpIjoiZWI1Zj... ) HHH-14102 ( https://hibernate.atlassian.net/browse/HHH-14102?atlOrigin=eyJpIjoiZWI1Zj... ) orphanRemoval behaviour differ from lazy to eager loading ( https://hibernate.atlassian.net/browse/HHH-14102?atlOrigin=eyJpIjoiZWI1Zj... ) Change By: Florian Kern ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ee102c... ) In a @ oneToMany relation you have different behaviours if you removing a children from the collection. If you remove a children from a fetched collection, the children wouldnt will not be removed deleted from the database. If your collection is lazy fetched, the children would will be deleted from the database. See attached Testcase for example. Execute via {code:java} mvn test {code} ( https://hibernate.atlassian.net/browse/HHH-14102#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14102#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#100133- sha1:bf400b0 )

5 years, 5 months

1
0
0 / 0

[JIRA] (HHH-14102) orphanRemoval behaviour differ from lazy to eager loading

by Florian Kern (JIRA)

5 years, 5 months

1
0
0 / 0

[JIRA] (HHH-14102) orphanRemoval behaviour differ from lazy to eager loading

by Florian Kern (JIRA)

Florian Kern ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ee102c... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjdlM2VkN2Uy... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14102?atlOrigin=eyJpIjoiYjdlM2... ) HHH-14102 ( https://hibernate.atlassian.net/browse/HHH-14102?atlOrigin=eyJpIjoiYjdlM2... ) orphanRemoval behaviour differ from lazy to eager loading ( https://hibernate.atlassian.net/browse/HHH-14102?atlOrigin=eyJpIjoiYjdlM2... ) Issue Type: Bug Affects Versions: 5.4.12, 5.4.17 Assignee: Unassigned Components: hibernate-core, hibernate-entitymanager Created: 09/Jul/2020 04:11 AM Priority: Critical Reporter: Florian Kern ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ee102c... ) In a oneToMany relation you have different behaviours if you removing a children from the collection. If you remove a children from a fetched collection, the children wouldnt be removed from the database. If your collection is lazy fetched, the children would be deleted. See attached Testcase for example. Execute via mvn test ( https://hibernate.atlassian.net/browse/HHH-14102#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14102#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#100133- sha1:bf400b0 )

5 years, 5 months

1
0
0 / 0

[JIRA] (WEBSITE-591) Broken link: http://hibernate.org/dtd/hibernate-configuration-5.2.0.dtd

by Website Form collector (JIRA)

5 years, 5 months

1
0
0 / 0

[JIRA] (HBX-2052) Investigate the use of 'hibernate-type=SomeUserType' in hibernate-reverse-engineering document

by Koen Aers (JIRA)

Koen Aers ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Tools ( https://hibernate.atlassian.net/browse/HBX?atlOrigin=eyJpIjoiNWY5MjgyZTI0... ) / Task ( https://hibernate.atlassian.net/browse/HBX-2052?atlOrigin=eyJpIjoiNWY5Mjg... ) HBX-2052 ( https://hibernate.atlassian.net/browse/HBX-2052?atlOrigin=eyJpIjoiNWY5Mjg... ) Investigate the use of 'hibernate-type=SomeUserType' in hibernate-reverse-engineering document ( https://hibernate.atlassian.net/browse/HBX-2052?atlOrigin=eyJpIjoiNWY5Mjg... ) Issue Type: Task Assignee: Koen Aers ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Created: 09/Jul/2020 03:35 AM Fix Versions: 6.0.0.Alpha1 Priority: Major Reporter: Koen Aers ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hibernate 6.0 does not seem to be happy with this particular piece of xml in the Hibernate reverse engineering xml file: <hibernate-reverse-engineering> <type-mapping> <sql-type jdbc-type= "VARCHAR" length= '20' hibernate-type= "SomeUserType" /> </type-mapping> ... </hibernate-reverse-engineering> The relevant section occurs in org.hibernate.tool.jdbc2cfg.OverrideBinder.TestCase. ( https://hibernate.atlassian.net/browse/HBX-2052#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HBX-2052#add-comment?atlOrigin=eyJ... ) 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#100133- sha1:bf400b0 )

5 years, 5 months

1
0
0 / 0

[JIRA] (HSEARCH-3950) Simpler configuration syntax for single-backend applications

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=eyJpIjoiNWM2NjRk... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3950?atlOrigin=eyJpIjoiNWM... ) HSEARCH-3950 ( https://hibernate.atlassian.net/browse/HSEARCH-3950?atlOrigin=eyJpIjoiNWM... ) Simpler configuration syntax for single-backend applications ( https://hibernate.atlassian.net/browse/HSEARCH-3950?atlOrigin=eyJpIjoiNWM... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Currently, a single-backend application will need to do this: {noformat} hibernate.search.default_backend = myBackend hibernate.search.backends.myBackend.foo = ... hibernate.search.backends.myBackend.bar = ... hibernate.search.backends.myBackend.foobar = ... {noformat} We could simplify it to this: {noformat} hibernate.search.backend.foo = ... hibernate.search.backend.bar = ... hibernate.search.backend.foobar = ... {noformat} This would be consistent with how [datasources|https://quarkus.io/guides/datasource] are configured in Quarkus, but unfortunately not with how [Hibernate Search backends|https://quarkus.io/guides/hibernate-search-elasticsearch] are configured in Quarkus. A few details: * We would have to give a name to this default backend. {{default}}, maybe? In that case we should forbid the use of that name for named backends. * Existing applications relying on default_backend should continue to work, but maybe we should deprecate this configuration property. People who really need to define the default backend at deployment time can use the programmatic mapping. * We should still allow the definition of named backends, but they will only be used when explicitly referenced. * We should use the default backend wherever possible in tests and documentation, and add separate tests and documention for named backends. * In examples for setting configuration properties, we should *only* include an example for the default backend. We'll just mention in the section about named backends how the prefix changes for those. ( https://hibernate.atlassian.net/browse/HSEARCH-3950#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3950#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#100133- sha1:bf400b0 )

5 years, 5 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 July 2020