April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HCANN-22) Problem with @ElementCollection or @CollectionTable in core/annotations 3.5.1 creating bogus unique key

by Lynn Keeling (JIRA)

Problem with @ElementCollection or @CollectionTable in core/annotations 3.5.1 creating bogus unique key ------------------------------------------------------------------------------------------------------- Key: HCANN-22 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-22 Project: Hibernate Commons Annotations Issue Type: Bug Environment: Hibernate Core/Annotions 3.5.1-Final MySQL 5.1 Reporter: Lynn Keeling I've encountered a problem that may be a hibernate collection bug. Using the code listed below, I'm creating a collection table that has two columns: TERRITORY_ID and characters_CHARACTER_ID. When hibernate creates the table, it creates the following indexes: 1. An compound unique index on TERRITORY_ID and characters_CHARACTER_ID, which is expected. 2. A non-unique on both TERRITORY_ID and characters_CHARACTER_ID, which is expected. 3. A unique index on characters_CHARACTER_ID, WHICH IS THE PROBLEM I"M REPORTING.. Why is the unique index on characters_CHARACTER_ID being created? If I manually drop the index, my code works fine. Otherwise, I get a unique constraint violation when I try to insert more than one of the same character id into the table. Not the desired behavior. public class Territory implements Serializable { private static final long serialVersionUID = -8906914598601073008L; @Id @Column(name = "TERRITORY_ID", length = 50) private String territoryId; @ElementCollection(fetch = FetchType.LAZY) @CollectionTable(name="TERRITORY_CHARACTER", joinColumns=@JoinColumn(name="TERRITORY_ID")) @Column(name="CHARACTER_ID") private Set<Character> characters; ... } public class Character implements Serializable { private static final long serialVersionUID = 845127746329423630L; @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "CHARACTER_ID") private Long characterId; ... } -- 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

14 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4837) 2L-Querycache: NaturalKeyLookup throws EntityNotFoundException

by Guenther Demetz (JIRA)

2L-Querycache: NaturalKeyLookup throws EntityNotFoundException -------------------------------------------------------------- Key: HHH-4837 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4837 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-Beta-3 Environment: 3.5.0-Beta3, HSQLDB, Ehcache as 2L-cache provider Reporter: Guenther Demetz Attachments: TestLookupNaturalIdOnDeletedEntity.jar A cached NaturalKeyLookup query (immutable NaturalId) looking for a entity which has already been deleted, throws EntityNotFoundException. This is different to the behavior with disabled 2L-Querycache where the query simply returns null. Please see attached Testcase for details. -- 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

14 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5172) Invalid alias when referencing two different tables in formula tags

by Stephen Visser (JIRA)

Invalid alias when referencing two different tables in formula tags ------------------------------------------------------------------- Key: HHH-5172 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5172 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Environment: mappings Reporter: Stephen Visser I have a complicated Hibernate entity which is defined as the join between two tables. It looks like the following: {quote} <hibernate-mapping> <class name="User" table="PERSONS"> <id name="personID" column="PERSON_ID"/> <property name="lmsUserName" column="WEB_USERNAME" /> <property name="userName" insert="false" update="false" unique="true"> <formula> coalesce(lower(WEB_USERNAME), lower(USERNAME)) </formula> </property> <join table="APPLICATION_USERS" optional="true"> <key column="PERSON_ID"/> <property name="sasUserName" column="USERNAME"/> </join> </class> </hibernate-mapping> {quote} We can find by criteria as shown below: {quote} final Criteria hibernateCriteria = session.createCriteria(User.class).add(Restrictions.eq("userName", "EXAMPLE_USERNAME")); final User retrievedObject = (User) hibernateCriteria.uniqueResult(); {quote} This results in the following SQL query being generated: {quote} select userimpl0_.PERSON_ID as PERSON1_2_0_, userimpl0_.WEB_USERNAME as WEB5_2_0_, userimpl0_2_.USERNAME as USERNAME4_0_, coalesce(lower(userimpl0_.WEB_USERNAME), lower(userimpl0_.USERNAME)) as formula0_0_, from PERSONS userimpl0_ left outer join APPLICATION_USERS userimpl0_2_ on userimpl0_.PERSON_ID=userimpl0_2_.PERSON_ID where coalesce(lower(userimpl0_.WEB_USERNAME), lower(userimpl0_.USERNAME)) = 'EXAMPLE_USERNAME' {quote} Due to the nature of our legacy data system, we are trying to find the userName in one of two columns in the DB. A user may have one or both of the user names specified. We want to query by userName in order to avoid making multiple queries. To do this, we make use of the coalesce function as shown above. The query created by retrieving by userName prepends both WEB_USERNAME and USERNAME in the coalesce function with a single alias. In fact, I need WEB_USERNAME to be prepended with the alias of the PERSONS table (this is done correctly) and USERNAME to be prepended by the alias for the APPLICATION_USERS table (this is where the problem lies). Ideally, I think it's reasonable to have one of two options: 1) Be able to 'escape' the automatic prepend of table aliases. This would work fine for me as I have no duplicate columns in this example. But I don't think that it is a very universal solution... 2) Be able to reference the alias for a given table using a well-defined syntax (i.e. {PERSONS}.USERNAME ) I've written a little bit here: https://forum.hibernate.org/viewtopic.php?t=1004224 -- 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

14 years, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4734) desc name column

by RAFAL MICHALAK (JIRA)

desc name column ---------------- Key: HHH-4734 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4734 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2 Environment: hibernate 3.5.0-beta2 and PostgreSQL 8.3 Reporter: RAFAL MICHALAK When use Entity with String desc name column, I got read error (PostgreSQL) @Entity @Table(name="test") class test { @Id private int id; private String desc; .... -- 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

14 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3005) DTD: map-key should allow nested type rather than attribute.

by Mattias Jiderhamn (JIRA)

DTD: map-key should allow nested type rather than attribute. ------------------------------------------------------------ Key: HHH-3005 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3005 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Reporter: Mattias Jiderhamn Priority: Minor The metamodel allows for user typed 'map-key's via nested <type> tags but the DTD requires a type, attribute. See HHH-822 for a similar problem with key-property. -- 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

14 years, 5 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-485) mvn site is currently not working (in ./hibernate-search)

by Emmanuel Bernard (JIRA)

mvn site is currently not working (in ./hibernate-search) --------------------------------------------------------- Key: HSEARCH-485 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-485 Project: Hibernate Search Issue Type: Bug Components: build Affects Versions: 3.2.0.Beta1 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 3.2.0 Emmanuel-MBP-15:hibernate-search manu$ mvn site [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Hibernate Search [INFO] task-segment: [site] [INFO] ------------------------------------------------------------------------ [INFO] [site:site {execution: default-site}] [INFO] Generating "Project Team" report. [INFO] Generating "Issue Tracking" report. [INFO] Generating "Dependency Management" report. [INFO] Generating "Continuous Integration" report. [INFO] Generating "Project Plugins" report. [INFO] Generating "Dependencies" report. [WARNING] The repository url 'http://people.apache.org/repo/m2-snapshot-repository' is invalid - Repository 'apache.snapshots' will be blacklisted. [WARNING] The repository url 'http://people.apache.org/repo/m2-incubating-repository/' is invalid - Repository 'apache-incubator' will be blacklisted. [INFO] Generating "Plugin Management" report. [INFO] Generating "Mailing Lists" report. [INFO] Generating "Source Repository" report. [INFO] Generating "Project Summary" report. [INFO] Generating "About" report. [INFO] Generating "Project License" report. [INFO] [jdocbook:translate {execution: make-doc}] can't find The next section demonstrates how to programmatically define analyzers. in he next section demonstrates how to programmatically define analyzers.</para> [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Unexpected problem Embedded error: uanble to execute po2xml : Process exited with an error: 1(Exit value: 1) [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 4 minutes 7 seconds [INFO] Finished at: Fri Apr 02 11:47:35 CEST 2010 [INFO] Final Memory: 59M/151M [INFO] ------------------------------------------------------------------------ -- 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

14 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-467) publish Maven artifacts containing the testsuite

by Sanne Grinovero (JIRA)

publish Maven artifacts containing the testsuite ------------------------------------------------ Key: HSEARCH-467 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-467 Project: Hibernate Search Issue Type: Task Components: build Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta2 -- 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

14 years, 5 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5041) @ManyToOne not working with @Formula

by Chris Wilson (JIRA)

@ManyToOne not working with @Formula ------------------------------------ Key: HHH-5041 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5041 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.0-CR-2 Reporter: Chris Wilson Attachments: HibernateAnnotationJoinOnFormulaTest.java HHH-4382 was marked as resolved fixed in 3.5. However, I cannot find the fix, and it appears still to be broken for me. The attached test case fails with 3.5.0-CR-2 just as it did with 3.3.2. It seems to ignore the @Formula annotation and simply create a productFamily column, which is of course empty. If I am doing something wrong, please could you tell me what it is, so that I can fix my code? -- 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

14 years, 5 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2584) PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map

by Daniel Wellman (JIRA)

PersistentMap.remove() incorrect on uninitialized, non-extra-lazy map --------------------------------------------------------------------- Key: HHH-2584 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2584 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.3, 3.2.2, 3.2.1 Environment: Hibernate 3.2.3 ga, MySQL 5.0.24a, for Win32 Reporter: Daniel Wellman Attachments: persistentmap_remove.patch This problem is nearly identical to HHH-2476: PersistentMap.put() incorrect on uninitialized, non-extra-lazy map. remove() has the same problem. See also issue HHH-2142. The write up for HHH-2476 was so concise that I will transform it here, substituting remove() for put(). --- Essentially, an uninitialized PersistentMap loses the first remove() into it if defined as non-extra-lazy. The underlying cause is the code in PersistentMap#remove() which attempts to readElementByIndex(). In the case of non-extra-lazy, readElementByIndex() returns the UNKNOWN marker object which is supposed to be used to signal that the delegate map is now initialized and to remove the element directly from the map. Long story short, PersistentMap#remove() does not properly check the return value from readElementByIndex() and react accordingly. -- 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

14 years, 5 months

8
12
0 / 0

[Hibernate-JIRA] Created: (HV-156) Exploring properties and cascade is unnecessary if TraversableResolver returns false

by Emmanuel Bernard (JIRA)

Exploring properties and cascade is unnecessary if TraversableResolver returns false ------------------------------------------------------------------------------------ Key: HV-156 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-156 Project: Hibernate Validator Issue Type: Improvement Reporter: Emmanuel Bernard This will likely optimize the engine. not at urgent though since HV-155 -- 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

14 years, 5 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2010