November 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (HHH-7749) Allow setting system properties for tests on gradle command line

by Steve Ebersole (JIRA)

13 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] (BVAL-293) Refinements around ConfigurationSource

by Gunnar Morling (JIRA)

13 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] (HBX-1214) Unable to generate Alter Scripts using hbm2ddl with update=true, for teradata tables

by RamyaJ (JIRA)

13 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] (HV-627) Programmatic API should honor element type of constraint annotations

by Gunnar Morling (JIRA)

13 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3795) Unexpected behaviour of saveOrUpdate() for associations with delete-orphan

by Fabian Dankof (JIRA)

Unexpected behaviour of saveOrUpdate() for associations with delete-orphan -------------------------------------------------------------------------- Key: HHH-3795 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3795 Project: Hibernate Core Issue Type: Improvement Environment: Hibernate 3.2.6.GA, PostgreSQL 8.3 Reporter: Fabian Dankof Hello there, I think saveOrUpdate() behaves somewhat unexpected for associations with delete-orphan cascading style: Prerequisite: Association is set to cascade="all,delete-orphan" and nullable=true 1) Within a single session (i.e. a transient object): * Load parent * Delete child * saveOrUpdate() Result: Child is deleted from DB, a DELETE statement was issued 2) Across multiple session (i.e. a detached object): * Have parent with valid ID, but empty list/set of children * saveOrUpdate() Result: Child is not deleted from DB, an UPDATE statement is issued which sets FK of child to 'null' 3) like 2) but nullable is FALSE Result: Nothing happens. With merge() everything works as expected for detached and transient instances. I would either expect saveOrUpdate() to completely disregard DELETE statements OR behave similar to merge(). At least the different results of case 1) and 2) are pretty confusing. Best regards, Fabian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3562) Support @OrderBy and @Sort annotations

by Adam Warski (JIRA)

Support @OrderBy and @Sort annotations -------------------------------------- Key: HHH-3562 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3562 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] (HHH-951) setMaxResults causes "ORA-00918: column ambiguously defined" exception

by Tom Terrace (JIRA)

13 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] (HHH-951) setMaxResults causes "ORA-00918: column ambiguously defined" exception

by Tom Terrace (JIRA)

13 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] (HHH-951) setMaxResults causes "ORA-00918: column ambiguously defined" exception

by Tom Terrace (JIRA)

13 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] (HHH-951) setMaxResults causes "ORA-00918: column ambiguously defined" exception

by Tom Terrace (JIRA)

13 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-issues November 2012