December 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2796) Generated version are incremented by Hibernate

by Heba Tawfik (JIRA)

Generated version are incremented by Hibernate ---------------------------------------------- Key: HHH-2796 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2796 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.1 Environment: 3.2.1, Oracle 10g Reporter: Heba Tawfik Creating a new entity which it's version is set to generated="always" & saving it, then in the same session adding an object to any of its on-to-many relationships is throwing a StaleObjectStateException. To regenerate the problem, consider the following code 1- departement.hbm.xml : ---------------------------------------- <hibernate-mapping package="com.myproject.domain"> <class name="Departement" table="Departement"> <id name="id"> <column name="dept_id" /> </id> <version column="version" generated="always" name="version" type="integer" unsaved-value="null" /> <property name="name" column="name" /> <bag name="employees" inverse="true" cascade="all" lazy="true"> <key column="dept_id"></key> <one-to-many class="Employee" /> </bag> </class> </hibernate-mapping> 2- employee.hbm.xml : -------------------------------------- <hibernate-mapping package="com.myproject.domain"> <class name="Employee" table="Employee"> <id name="id"> <column name="employee_id" /> </id> <property name="firstName" column="first_name" /> <property name="lastName" column="last_name" /> <property name="age" column="age" /> <property name="salary" column="salary" /> <many-to-one cascade="none" class="com.myproject.domain.Departement" column="dept_id" embed-xml="true" insert="false" name="department" not-null="false" unique="false" update="false" not-found="ignore"> </many-to-one> </class> </hibernate-mapping> 3- Departement.Java --------------------------- package com.myproject.domain; import java.util.ArrayList; import java.util.List; public class Departement extends BaseDepartement{ int id; String name; List employees; Integer version; public int getId() { return id; } public void setId(int id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } public Integer getVersion() { return version; } public void setVersion(Integer version) { this.version = version; } public List getEmployees() { return employees; } public void setEmployees(List employees) { this.employees = employees; } public void addToEmployeeList(Employee emp) { if(employees==null) { setEmployees(new ArrayList()); } employees.add(emp); } } 4- Employee.Java : --------------------------- package com.myproject.domain; public class Employee { int id; String firstName; String lastName; int age; int salary; BaseDepartement department; public BaseDepartement getDepartment() { return department; } public void setDepartment(BaseDepartement department) { this.department = department; } public int getAge() { return age; } public void setAge(int age) { this.age = age; } public String getFirstName() { return firstName; } public void setFirstName(String firstName) { this.firstName = firstName; } public int getId() { return id; } public void setId(int id) { this.id = id; } public String getLastName() { return lastName; } public void setLastName(String lastName) { this.lastName = lastName; } public int getSalary() { return salary; } public void setSalary(int salary) { this.salary = salary; } } 4- Code To Test : ------------------------ public static void main(String args[]) throws Exception { SessionFactory factory = new Configuration().configure("com/myproject/config/hibernate.cfg.xml").buildSessionFactory(); Session session = factory.openSession(); Transaction transaction = session.beginTransaction(); Departement aDept =new Departement(); aDept.setId(10); aDept.setName("Test"); session.save(aDept); transaction.commit(); transaction = session.beginTransaction(); Employee emp=new Employee(); emp.setId(10); emp.setFirstName("test"); emp.setLastName("test"); emp.setSalary(10); emp.setAge(10); emp.setDepartment(aDept); aDept.addToEmployeeList(emp); session.saveOrUpdate(aDept); transaction.commit(); session.close(); } On the database, the default value for version cloumn is set to "1" and a trigger is defined as follow on the Departement table: create or replace TRIGGER TRIGGER1 BEFORE UPDATE ON DEPARTEMENT FOR EACH ROW BEGIN :new.version:= :old.version + 1; END; Upon executing the above code, the following is the hibernate logging : automatically flushing session /* insert com.eds.myproject.domain.Departement */ insert into Departement (name, dept_id) values (?, ?) binding 'Test' to parameter: 1 binding '10' to parameter: 2 /* get generated state com.eds.myproject.domain.Departement */ select departemen_.version as version1_ from Departement departemen_ where departemen_.dept_id=? binding '10' to parameter: 1 returning '1' as column: version1_ before transaction completion after transaction completion automatically flushing session /* get current state com.eds.myproject.domain.Employee */ select employee_.employee_id, employee_.first_name as first2_0_, employee_.last_name as last3_0_, employee_.age as age0_, employee_.salary as salary0_ from Employee employee_ where employee_.employee_id=? binding '10' to parameter: 1 /* insert com.eds.myproject.domain.Employee */ insert into Employee (first_name, last_name, age, salary, employee_id) values (?, ?, ?, ?, ?) binding 'test' to parameter: 1 binding 'test' to parameter: 2 binding '10' to parameter: 3 binding '10' to parameter: 4 binding '10' to parameter: 5 /* update com.eds.myproject.domain.Departement */ update Departement set name=? where dept_id=? and version=? binding 'Test' to parameter: 1 binding '10' to parameter: 2 binding '2' to parameter: 3 Could not synchronize database state with session org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [com.eds.myproject.domain.Departement#10] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1714) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2357) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2257) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2557) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at com.eds.myproject.test.Test.main(Test.java:43) org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [com.eds.myproject.domain.Departement#10] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1714) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2357) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2257) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2557) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at com.eds.myproject.test.Test.main(Test.java:43) -- 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

11 years, 6 months

4
4
0 / 0

[Hibernate-JIRA] (WEBSITE-17) Observation on composite primary key comments on "1.2.4. Collection of values"

by Andreas Tasoulas (JIRA)

11 years, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-7243) Wrong SQL statement generated due to a name collision of column aliases

by Gerald Brose (JIRA)

Wrong SQL statement generated due to a name collision of column aliases ----------------------------------------------------------------------- Key: HHH-7243 URL: https://hibernate.onjira.com/browse/HHH-7243 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 3.6.10, 3.6.9 Environment: Hibernate 3.6.9.Final, MS SQL Server 2008 R2, (Spring, JPA2) Reporter: Gerald Brose Priority: Critical Under certain conditions, Hibernate generates a wrong SQL query due to a name collision of the generated column aliases used when accessing collections. This is done in the class AbstractCollectionPersister, which creates the same column alias (in our case the alias is "SUCHMASKE8_") for an index column (original column name: "SUCHMASKE_ORDER") and a foreign key column ("SUCHMASKE") in a OneToMany association. As a consequence, the resulting SQL statement selects from only one of the required columns. (In our case, this results in the integer value of a FK being used as a collection index, which in turn leads to a huge collection all initialized with null values). Some information on the mapping: from entity class SUCHMASKE: @JoinColumn(name="SUCHMASKE") @OneToMany @OrderColumn(name="SUCHMASKE_ORDER") public List<Suchkriterium> getSuchkriterien() { return suchkriterien; } from entity class Suchkriterium: @ManyToOne(fetch = FetchType.LAZY) @JoinColumn(name = "SUCHMASKE") @MetaModelName("Suchmaske") public Suchmaske getSuchmaske() { return suchmaske; } Both entity classes share the same ancestor class in the inheritance hierarchy, strategy is joined inheritance. There is no join table. The @JoinColumn is used work around the well-known Hibernate limitation that OrderColumns are not updated if specified on the non-owning side. Analysis: This alias name collision occurs in the case where both the unique integers used to create the aliases are the same (here: "8"). In one case this integer is coming from the root table in an inheritance hierarchy, in the other case from the column itself). Additionally, the two original column names share the same prefix ("SUCHMASKE"). Both these conditions are IMO completely legal. The integer value collision is somewhat random (so it took us days to identify the problem...). The prefix match is a even a regular naming scheme for order columns that correspond to an association. The actual problem is that Hibernate uses slightly different ways to create these alias names for key columns and index columns (cf. AbstractCollectionPersister, lines 299 and 387, respectively). As a workaround, we have to use an additional column naming convention for order columns so that common prefixes are avoided. This means we have to modify our existing schema and application, which is a nuisance. A bug fix in Hibernate would obviously be preferable. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-726) Facetted search on embedded collections takes only first element from collection

by Elmer van Chastelet (JIRA)

Facetted search on embedded collections takes only first element from collection -------------------------------------------------------------------------------- Key: HSEARCH-726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-726 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.4.0.CR2, 3.4.0.CR1, 3.4.0.Beta1, 3.4.0.Alpha1 Environment: Any valid config I suppose, tested using Hibernate Core 3.6.3 + Search 3.4.0.CR2, mysql and in Hibernate Search test environment Reporter: Elmer van Chastelet Attachments: EmbeddedCollectionsFacetsTest.zip >From [Hibernate Search Forum: Bug or not? Faceted search + embedded fields (*tomany)|https://forum.hibernate.org/viewtopic.php?f=9&t=1010472&start=0]. Faceted search won't work correctly when used on collections. For the cause I quote Hardy Ferentschik : ??The current faceting implementation utilizes the Lucene FieldCache which has a limitation that each document must have a single value for the specified field.?? I can think of many use cases in which faceted search on collections is really needed, some examples: Facetting on authors when searching for publications Facetting on ingredients when searching for recipes Facetting on actors when searching for movies ... Attached is a hibernate search test case. It fails on retrieving the right amount of matched authors. Currently I don't have the needed insight to suggest an improvement on current implementation to make it compatible with collections. Hopefully it can be achieved with small changes. Good luck :) -- 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

11 years, 6 months

5
9
0 / 0

[Hibernate-JIRA] (HHH-7804) Unique constraint no longer applied on @Column(unique = true, nullable = false)

by Luke Carroll (JIRA)

11 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] (HHH-7806) Failure of lazy initialization of collection no longer reports role

by Shawn Clowater (JIRA)

11 years, 6 months

2
4
0 / 0

[Hibernate-JIRA] (HHH-7811) grammar error in devguide for HB

by simar mugattarov (JIRA)

11 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] (HHH-7813) mistake in code examples in devguide for HB

by simar mugattarov (JIRA)

11 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] (HHH-7715) org.hibernate.id.IncrementGenerator very slow

by Andy flury (JIRA)

11 years, 6 months

2
7
0 / 0

[Hibernate-JIRA] (HHH-7826) Generate 'unique' constraints in stable order

by Neukomm (JIRA)

11 years, 6 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2012