July 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4580) Possible Sybase bug causes AssertionFailure in QueryByExampleTest

by Strong Liu (JIRA)

Possible Sybase bug causes AssertionFailure in QueryByExampleTest ----------------------------------------------------------------- Key: HHH-4580 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4580 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.2.4.sp1 Environment: sybase 15 Reporter: Strong Liu Test QueryByExampleTest.testJunctionNotExpressionQBE fails due to a possible bug in Sybase 15. The same test passes for Sybase 12.5. The test expects two records as a result for a query, but it gets 3. After some debugging with the query that Hibernate generated, I end up with these two simpler ones: select id from Componentizable where not (name like ? and subName1 like ?) select id from Componentizable where not (name like 'hibernate' and subName1 like 'ope%') The first one returns three records, while the second returns two. The interesting part is that if I replace the first parameter in the first query by a hardcoded value ("hibernate"), it still returns 3 records. That means that the problem is probably with the binding of JDBC parameters containing a wildcard % . -- 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, 7 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5894) [ENVERS] Loading collections from envers entity fails due to QueryException

by Sven Rienstra (JIRA)

[ENVERS] Loading collections from envers entity fails due to QueryException --------------------------------------------------------------------------- Key: HHH-5894 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5894 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.1 Environment: Hibernate 3.6.1 Oracle 10g Ubuntu Reporter: Sven Rienstra Priority: Blocker When I'm trying to load a collection from an envers entity it fails due to an incorrect HQL query: Caused by: org.hibernate.QueryException: could not resolve property: domein_id of: nl.protopics.zwip.model.gvo.Faq_AUD [select e from nl.protopics.zwip.model.gvo.Faq_AUD e where e.domein_id = :domein_id and e.originalId.REV.id = (select max(e2.originalId.REV.id) from nl.protopics.zwip.model.gvo.Faq_AUD e2 where e2.originalId.REV.id <= :revision and e.originalId.id = e2.originalId.id) and REVTYPE != :delrevisiontype] at org.hibernate.persister.entity.AbstractPropertyMapping.propertyException(AbstractPropertyMapping.java:81) at org.hibernate.persister.entity.AbstractPropertyMapping.toType(AbstractPropertyMapping.java:75) at org.hibernate.persister.entity.AbstractEntityPersister.toType(AbstractEntityPersister.java:1465) at org.hibernate.hql.ast.tree.FromElementType.getPropertyType(FromElementType.java:315) at org.hibernate.hql.ast.tree.FromElement.getPropertyType(FromElement.java:487) at org.hibernate.hql.ast.tree.DotNode.getDataType(DotNode.java:611) at org.hibernate.hql.ast.tree.DotNode.prepareLhs(DotNode.java:263) at org.hibernate.hql.ast.tree.DotNode.resolve(DotNode.java:210) at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:117) at org.hibernate.hql.ast.tree.FromReferenceNode.resolve(FromReferenceNode.java:113) at org.hibernate.hql.ast.HqlSqlWalker.resolve(HqlSqlWalker.java:880) at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1330) at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4471) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3944) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:2047) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1972) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1972) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:831) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:617) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:301) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:244) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:254) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:185) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:124) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1770) at org.hibernate.envers.entities.mapper.relation.query.OneAuditEntityQueryGenerator.getQuery(OneAuditEntityQueryGenerator.java:99) at org.hibernate.envers.entities.mapper.relation.lazy.initializor.AbstractCollectionInitializor.initialize(AbstractCollectionInitializor.java:62) at org.hibernate.envers.entities.mapper.relation.lazy.proxy.CollectionProxy.checkInit(CollectionProxy.java:50) at org.hibernate.envers.entities.mapper.relation.lazy.proxy.CollectionProxy.iterator(CollectionProxy.java:70) mappings: Domein class, from where I call getFaqs() @OneToMany(cascade = CascadeType.ALL, mappedBy = "domein") private List<Faq> faqs = new ArrayList<Faq>(); Faq mapping: @ManyToOne private Domein domein; Works fine with 3.6.0. -- 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, 7 months

4
12
0 / 0

[Hibernate-JIRA] Created: (ANN-814) OneToOne Unidirectional Support

by Rachit (JIRA)

OneToOne Unidirectional Support ------------------------------- Key: ANN-814 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-814 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Oracle 10g, Java 1.5 Reporter: Rachit Priority: Blocker I tried hard for unidirectional OneToOne mapping as below: @Entity @Table(name = "PARTY") public class Party{ private Person person; private String key; @OneToOne(fetch = FetchType.EAGER, cascade = CascadeType.ALL,) @PrimaryKeyJoinColumn(name = "PARTY_ID", referencedColumnName = "PERSON_PARTY_ID") public Person getPerson() { return person; } public void setPerson(Person person) { this.person = person; } @Id @GeneratedValue(generator = "system-uuid") @GenericGenerator(name = "system-uuid", strategy = "uuid") @Column(name = "PARTY_ID", nullable = false) public String getKey() { return key; } private void setKey(String key) { this.key = key; } } and it is one-to-one mapped to Person as: @Entity(name = "Person") @Table(name = "PERSON") public class Person { private String key; @Id @Column(name = "PERSON_PARTY_ID") public String getKey() { return key; } public void setKey(String key) { this.key = key; } } Now in Person, I deliberately dont have sysUUID as generated as then it generates a unique value for person and the association gets lost. With this mapping hibernate throws the following exception : Caused by: org.hibernate.id.IdentifierGenerationException: ids for this class must be manually assigned before calling save(): Person. I read and saw constrained="true" being used in mapping files, which I couldnt use as there is no attribute like it in OneToOne annotation. Please help me out on this -- 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, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-820) Document limitations and workarounds for JVM bug affecting Lucene users

by Sanne Grinovero (JIRA)

Document limitations and workarounds for JVM bug affecting Lucene users ----------------------------------------------------------------------- Key: HSEARCH-820 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-820 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Priority: Minor Fix For: 3.4.1, 4.0 We should but a notice in the documentation about https://issues.apache.org/jira/browse/LUCENE-3335 especially which JVM tuning parameters should be used; this is especially relevant to Java7 since its enabled by default, but possible to trigger on Java6 too (see bugdatabase http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7070134) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-662) Re-indexing failure in @IndexedEmbedded entities in @ManyToOne relationship

by Kyrill Alyoshin (JIRA)

Re-indexing failure in @IndexedEmbedded entities in @ManyToOne relationship --------------------------------------------------------------------------- Key: HSEARCH-662 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-662 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.3.0.Final Environment: Hibernate 3.6.0 Reporter: Kyrill Alyoshin Priority: Blocker Attachments: hibernate_search_bug.zip What is happening seems to be this: Let's say we have an @Indexed entity called Son. It has @IndexedEmbedded parent property called Dad in @ManyToOne relationship. Dad is @ContainedIn and has @Field on one of its fields. I am demonstrating a condition when more than one Dads are updated in a single session, only one would be re-indexed, the rest will fail to be re-indexed. I am attaching a simple IDEA project that clearly demonstrates what is going on. I believe that this is a very serious bug. (Note: I removed hibernate-3.6.0.jar from the lib directory to minimize the size of the zip file under 10M, the rest of the jars are there). Please run BugDemonstrationTest#showBug test method to see everything. -- 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, 7 months

4
13
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-811) Update dependencies for branch 3.4.x

by Sanne Grinovero (JIRA)

Update dependencies for branch 3.4.x ------------------------------------ Key: HSEARCH-811 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-811 Project: Hibernate Search Issue Type: Task Components: build Reporter: Sanne Grinovero Priority: Minor Fix For: 3.4.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5848) Columns's table name not processed by naming strategy

by Miroslav Havram (JIRA)

Columns's table name not processed by naming strategy ----------------------------------------------------- Key: HHH-5848 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5848 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Environment: Hibernate Core 3.6.0.Final JDK 1.6_u23 Reporter: Miroslav Havram When table name is specified within Column annotation, it is not processed by naming strategy. -- 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, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4727) Add option to specify foreign key name on table with shared primary key used in one-to-one relationship

by Pavla Nováková (JIRA)

Add option to specify foreign key name on table with shared primary key used in one-to-one relationship --------------------------------------------------------------------------------------------------------- Key: HHH-4727 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4727 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.2 Reporter: Pavla Nováková There is currently no way to specify (user friendly) foreign key name on table with shared primary key used in One-to-One mapping. The most intuitive way would be to accept @ForeignKey on property level (see the comment in the code below) or on entity level (similar way to usage in joined inheritance) or last option may be add parameter in foreign generator. {code} @Entity public class ExampleEntity implements Serializable { @Id @GenericGenerator(name = "foreign-generator", strategy = "foreign", parameters=@Parameter(name="property", value="parentExampleEntity")) @GeneratedValue(generator = "foreign-generator") private Long id; ... @PrimaryKeyJoinColumn @OneToOne(fetch=FetchType.LAZY, optional=false) @org.hibernate.annotations.ForeignKey(name="parent_entity_fk") // this is currently ignored private ParentExampleEntity parentExampleEntity; ... } {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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-667) Foreign key name on @OneToOne

by Immo Heikkinen (JIRA)

Foreign key name on @OneToOne ----------------------------- Key: ANN-667 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-667 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate Core 3.2.5.GA , Hibernate Annotations 3.3.0.GA, Sybase ASE 15 Reporter: Immo Heikkinen Priority: Minor Attachments: Child.java, Parent.java Foreign key constraint name cannot be changed using @org.hibernate.annotations.ForeignKey on a @OneToOne with foreign key. It doesn't matter which class is annotated with @ForeignKey. Please find the test case as an attachment. Original thread on the user forum: http://forum.hibernate.org/viewtopic.php?p=2367400 -- 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, 7 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6011) Issue with HQL Update query with <join> element

by Ganesh Shirsat (JIRA)

Issue with HQL Update query with <join> element ----------------------------------------------- Key: HHH-6011 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6011 Project: Hibernate Core Issue Type: Bug Components: core, query-hql Affects Versions: 3.6.0, 3.3.2 Environment: Hibernate 3.3.2 and Hibernate 3.6, Oracle, Window XP SP2 Reporter: Ganesh Shirsat Two table are connected using <join> element. There is primary table and secondary table. Trying to update the field using HQL query. it is throwing the error. for more details. Please click on below link. https://forum.hibernate.org/viewtopic.php?f=1&t=1009823 -- 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, 7 months

3
3
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 July 2011