June 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2503) AbstractEntityPersister swallows JDBCExceptions in processGeneratedProperties

by Dag Liodden (JIRA)

AbstractEntityPersister swallows JDBCExceptions in processGeneratedProperties ----------------------------------------------------------------------------- Key: HHH-2503 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2503 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1, 3.2.2, 3.2.3 Environment: 3.2.2GA and trunk Reporter: Dag Liodden Seems to be a small typo on line 3718 in AbstractEntityPersister (trunk and 3.2.2 GA) which makes exceptions during property generation being logged but not thrown: catch( SQLException sqle ) { JDBCExceptionHelper.convert( getFactory().getSQLExceptionConverter(), sqle, "unable to select generated column values", selectionSQL ); There should be a throw in there I guess. :) catch( SQLException sqle ) { throw JDBCExceptionHelper.convert( getFactory().getSQLExceptionConverter(), sqle, "unable to select generated column values", selectionSQL ); This bug will not be noticeable in most cases and is probably why it hasn't been detected / fixed so far. The method in question (processGeneratedProperties) is used for retrieving properties that are marked as "generated" in the mapping document / annotations - in other words any value that the database provides and is considered "read-only" from the Hibernate application's point of view. The generated value is retrieved by an extra select statement executed by Hibernate after an entity has been inserterd and / or updated (according to how the generated property is flagged). In my particular case, a property (not a key) is marked as generated="insert", so after Hibernate inserts a new entity to the database, it will immediately do a select and set the generated property to the value the database returns. Only in rare cases will this select fail in any way - in fact, I cannot think of any situations other than mapping errors (e.g getInt on a CHAR column) that can cause errors in this last select. That is in addition to my situation - a deadlock. My entity class uses uuid.hex generator for the PK, but at one point, we introduced a second unique key due to purely aestethic reasons. This is a SQL Server identity column. Since we don't do any explicit table locking during the inserts, we end up with deadlocks every time the following happens: T1: INSERT INTO TABLE (ID) values (?) T2: INSERT INTO TABLE (ID) values (?) T2: SELECT GENERATED_ID FROM TABLE WHERE ID = ? -- T1's insert hasn't been committed, so what should the the generated ID be? Deadlock! T1: SELECT GENERATED_ID FROM TABLE WHERE ID = ? ... SQL Server throws an error to indicate the deadlock, but due to the missing throw in the processGeneratedProperties-method, it is never shown to the process doing the insert. The generated property is not set and retains it's null (or 0 in case of a primitive) without the business logic ever knowing that the entity could not be saved. -- 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

18 years, 8 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2320) Regression: optional properties under a <join> tag no longer update properly

by Chris Jones (JIRA)

Regression: optional properties under a <join> tag no longer update properly ---------------------------------------------------------------------------- Key: HHH-2320 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2320 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1, 3.2.0.cr4, 3.2.0.ga, 3.2.0.cr5 Environment: hibernate 3.2.0.cr4 through 3.2.1.ga hsql 1.8.0.7 and Oracle 9i Reporter: Chris Jones This was specifically introduced with the revision 10217 changes on the 3.2 branch in src/org/hibernate/persister/entity/AbstractEntityPersister.java Given the following setup: <class name="Thing"> <id .../> <join table="JOIN_TABLE" optional="true"> <key column="THING_ID" not-null="true"/> <property name="joinedProperty" column="JOINED_PROPERTY"/> </join> </class> scenario: Thing thing1 = new Thing(); thing1.setJoinedProperty("thing1"); save(thing1); // a record in the JOIN_TABLE is created properly and updates on the property can occur Thing thing2 = new Thing(); thing2.setJoinedProperty(null); save(thing2); // no record in JOIN_TABLE is created thing2.setJoinedProperty("thing2"); save(thing2); // in revision 10216, hibernate correctly runs an INSERT to create a JOIN_TABLE record with the value "thing2" // in revision 10217, hibernate incorrectly runs an UPDATE to try and update a non-existant record in the JOIN_TABLE with the thing2 id It looks like the expectation.verifyOutcome() method should be throwing a StaleStateException if the attempted update effects 0 rows. I will try and get an official hibernate testcase going and possibly a patch, but I wanted to enter this now in case there is something I'm missing that makes this change in functionality intentional. -- 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

18 years, 8 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2591) MySQL 5.0.12+ JOIN Syntax Changed

by Brian Rozmierski (JIRA)

MySQL 5.0.12+ JOIN Syntax Changed --------------------------------- Key: HHH-2591 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2591 Project: Hibernate3 Issue Type: Bug Components: query-hql, query-sql Affects Versions: 3.2.3, 3.2.1 Environment: Tested with Hibernate Core 3.2.1 and 3.2.3, MySQL 5.0.27, 5.0.33, 5.0.37 Reporter: Brian Rozmierski Priority: Critical With 5.0.12 MySQL changed the JOIN syntax to be SQL:2003 compliant. (See MySQL 5.0.12 Release Notes at http://dev.mysql.com/doc/refman/5.0/en/news-5-0-12.html and JOIN syntax information at http://dev.mysql.com/doc/refman/5.0/en/join.html for more information) Previous to this change the following query was valid: SELECT * FROM t1, t2 JOIN t3 ON (t1.i1 = t3.i3); Now it must be written as: SELECT * FROM (t1, t2) JOIN t3 ON (t1.i1 = t3.i3); or SELECT * FROM t1 JOIN t2 JOIN t3 ON (t1.i1 = t3.i3); -- 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

18 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2289) CLONE -Support new MySQL 5.0.12 join syntax

by Peter Lundberg (JIRA)

CLONE -Support new MySQL 5.0.12 join syntax ------------------------------------------- Key: HHH-2289 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2289 Project: Hibernate3 Type: New Feature Components: query-sql Versions: 3.1.2 Reporter: Peter Lundberg http://dev.mysql.com/doc/refman/5.0/en/join.html "Beginning with MySQL 5.0.12, natural joins and joins with USING, including outer join variants, are processed according to the SQL:2003 standard. These changes make MySQL more compliant with standard SQL. However, they can result in different output columns for some joins. Also, some queries that appeared to work correctly in older versions must be rewritten to comply with the standard. The following list provides more detail about several effects of the 5.0.12 change in join processing. The term "previously" means "prior to MySQL 5.0.12." Using 5.0.18 and hibernate 3.1.2, hibernate is not producing the correct join syntax for the latest versions of mysql. For example: FROM tableA AS A, tableB AS B INNER JOIN tableC AS C ON A.field1 = C.field2 The above fails, because the B JOIN C is evaluated before the A alias has been created. The solution is to use parentheses to force an order of evaluation: FROM (tableA AS A, tableB AS B) INNER JOIN tableC AS C ON A.field1 = C.field2 -- 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

18 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2106) * criteria queries

by Toby (JIRA)

* criteria queries ------------------ Key: HHH-2106 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2106 Project: Hibernate3 Type: New Feature Components: query-criteria Reporter: Toby -localArea -wideArea - country Imagine you want to query local area that belong to a country, independet of the "wide area". But country is only references via a wide area and there is no direct link between local area and a country. You can not add wide area as a restriction as the problem ist, that you want all wide areas....and you only need them to get to the county..... Criteria c = session.createCriteria(LocalArea.class); c.add(Restrictions.eq("wideArea", *)); c.add(Restrictions.eq("country", country)); -- 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

18 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2572) NullPointerException when cascade-merge detached entity graph that contains null component property

by Nguyen Hau Giang (JIRA)

NullPointerException when cascade-merge detached entity graph that contains null component property --------------------------------------------------------------------------------------------------- Key: HHH-2572 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2572 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: hibernate 3.2.3 only Reporter: Nguyen Hau Giang Priority: Critical Attachments: testCase.zip when merging detached entity graph whose leaf-entity contains null-component property, hibernate 3.2.3 will throw NPE. (leaf-entity level>2) No exception was thrown in hibenate 3.2.2 Mapping: Parent -> Child -> GrandChild All associations is cascade. GrandChild contains a component property. Test Case: parent=<load>; child=parent.get1Child(); GrandChild grandChild=new GrandChild(); grandChild.setComponent(null); child.add(grandChild); evict(parent);//session is closed ... merge(parent);//merge in new sesson -> THROW NullPointerException for further detail, see attache test case. -- 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

18 years, 8 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2675) Session.contains() always return false

by Mohammad Shoaib Ashrafi (JIRA)

Session.contains() always return false -------------------------------------- Key: HHH-2675 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2675 Project: Hibernate3 Issue Type: Bug Components: build Affects Versions: 3.1.3 Environment: JDK1.5, Tomcat6.0 Hibernate 3, Windows XP Reporter: Mohammad Shoaib Ashrafi i have two class (User and Role) with hibernate one-to-one mapping in runtime i load the user object after this i create the new user object with same primary key as loaded object and when i call session.update(newUser) then it throws NonUniqueObjectException so i added some statement before update if( session.contains(userObject) ){ session.evict(userObject) } session.update(userObject) but the problem is here that session.contains(userObject) always return false kindly resolved this issue and give the chance of thanks Regards Mohammad Shoaib Ashraif -- 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

18 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2164) Minor bug in section "20.1.1. Customizing the schema"

by Andres Gonzalez (JIRA)

Minor bug in section "20.1.1. Customizing the schema" ----------------------------------------------------- Key: HHH-2164 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2164 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0.ga Reporter: Andres Gonzalez Where it says: ******************************************************************************************************************************* A unique-key attribute may be used to group columns in a single unique key constraint. Currently, the specified value of the unique-key attribute is not used to name the constraint in the generated DDL, only to group the columns in the mapping file. <many-to-one name="org" column="orgId" unique-key="OrgEmployeeId"/> <property name="employeeId" unique-key="OrgEmployee"/> ******************************************************************************************************************************* i think the unique-key attributes should jave both the same value ("OrgEmployee", for example) -- 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

18 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2601) Missing documentation in section 5.1.12

by Chris Bredesen (JIRA)

Missing documentation in section 5.1.12 --------------------------------------- Key: HHH-2601 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2601 Project: Hibernate3 Issue Type: Bug Components: documentation Affects Versions: 3.2.3 Reporter: Chris Bredesen Priority: Minor Section "5.1.12. many-to-one" lists (15) after the formula="" part, but never gives documentation on what (15) is. The list below stops at (14). -- 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

18 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2583) inconsistency in case sensitivity of dialect registered keywords

by Pete Cassin (JIRA)

inconsistency in case sensitivity of dialect registered keywords ---------------------------------------------------------------- Key: HHH-2583 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2583 Project: Hibernate3 Issue Type: Bug Components: documentation, query-hql Affects Versions: 3.2.3 Reporter: Pete Cassin Priority: Minor Right now, the Dialect.registerKeyword() method seems to add a given Keyword to the set as is, without taking the lower case. This would be fine if the intent was to allow case sensitive keywords, however it becomes problematic when these dialect specified keywords are used by the method Template.isFunctionOrKeyword() - the tokens passed to this method always have toLowerCase() called on them prior to being passed in. Thus, if I create a keyword "someKeyword" It will never be recognized as such because even if I included it in my hql with identical case, that method will always be checking the dialect's keyword set for "somekeyword". thus, HQL passed into Template.renderWhereStringTemplate will end up incorrectly qualifying the keyword with a table name. This isn't a serious bug by any means, but it may be good to at least note in documentation that user-specified keywords have to be all lowercase in order to function properly. -- 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

18 years, 8 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2007