December 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-869) SchemaUpdateTask does not actually APPLY the DDL on Mysql 5.0

by Schwark Satyavolu (JIRA)

SchemaUpdateTask does not actually APPLY the DDL on Mysql 5.0 ------------------------------------------------------------- Key: HBX-869 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-869 Project: Hibernate Tools Type: Bug Components: ant Versions: 3.2beta9 Environment: Mysql 5.0, windows Reporter: Schwark Satyavolu Priority: Critical The ant task in verbose mode shows that the table does not exist, prints the ddl for the create table, but in fact does NOT create the table. Yet, the build is reported successful. -- 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
2
0 / 0

[Hibernate-JIRA] Created: (HV-76) Field annotated member validators does not work with proxied objects

by Lucien Weller (JIRA)

Field annotated member validators does not work with proxied objects --------------------------------------------------------------------- Key: HV-76 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-76 Project: Hibernate Validator Issue Type: Bug Affects Versions: 3.1.0.CR1, 3.0.0.ga Reporter: Lucien Weller Attachments: proxy-fix.patch, testcase.tar.gz Copied from subtask HV-68 as subtask of closed issue HV-64 seams not to appear as open issue): May be annotating validation constraints on field level ist not the best solution, but by now it's explicitly mentioned as a possibility without other indication of restrictions in hibernate validator doc. But obviously this method is not safe with hibernate proxy instances as it is demonstrated be test case attached to original issue (http://opensource.atlassian.com/projects/hibernate/secure/attachment/1409...). My first patch was a quick fix that worked for our case and a agree once again that it may have some side effects as it changes the semantic of field annotation. but my second solution (http://opensource.atlassian.com/projects/hibernate/secure/attachment/1409...) leaves every thing as it is and just handles proxy instances differently and produce a more correct validation result than in current version. I hope that you can do something with my ideas or a least document this limitation when using field annotation. -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2288) Adding a new ResultTransformer, permitting to instantiate and fill related beans and not to take care of aliases case.

by Nicolas Billard (JIRA)

Adding a new ResultTransformer, permitting to instantiate and fill related beans and not to take care of aliases case. ---------------------------------------------------------------------------------------------------------------------- Key: HHH-2288 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2288 Project: Hibernate3 Type: Improvement Components: query-sql, query-hql, query-criteria Versions: 3.2.1 Environment: Developped based on hibernate v 3.2.1 Reporter: Nicolas Billard Priority: Minor Attachments: ResultTransformerImprovement.zip Are joined to this post 2 classes. Below is the javadoc header of the ResultTransformer class. May be this could be integrated in next hibernate versions ( certainly with improvements ... :p ) Let me know if anyone finds it useful ... ------------------------------------------------------ * Transforms resultset to value a bean, via setters. * * Examples: * * bean MyBean as 2 setters : * - setId : takes an Integer * - setProduct : takes a Product bean * * Product bean as 2 setters : * - setId * - setLib * * resultset may have these columns : * - ID * - PRODUCT_ID * - PRODUCT_LIB * * A MyBean instance will be created for each tupple, * and a Product instance will be also created, filled with PRODUCT_ID and PRODUCT_LIB values. -- 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-4615) index() not working with maps and map-key-many-to-many

by Michael Wyraz (JIRA)

index() not working with maps and map-key-many-to-many ------------------------------------------------------ Key: HHH-4615 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4615 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.2, 3.2.7 Reporter: Michael Wyraz I have 2 mapped entities: EntityA [ id:long, testMap:Map<EnityB,Integer>, some other properties ] EntityB [ id:long, some other properties ] The mapping of EntityA is like: <class name="EntityA"> <id name="id">...</id> <map name="testMap" table="a_to_b"> <key column="a_id"/> <map-key-many-to-many column="b_id" class="EntityB"/> <element type="integer" column="int_value"/> </map> </class> Now I want to query all EntityA with a certain EnityB as map key: 1. "from a EntityA left join a.testMap b where index(b).id=?" Parameter: <Long> (id of an EntityB) 15:35:12,349 ERROR PARSER:56 - <AST>:1:94: unexpected AST node: ( java.lang.NullPointerException at org.hibernate.hql.ast.HqlSqlWalker.lookupProperty(HqlSqlWalker.java:534) at org.hibernate.hql.antlr.HqlSqlBaseWalker.addrExpr(HqlSqlBaseWalker.java:4543) at org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1289) at org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4243) at org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3722) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1864) at org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1792) at org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:818) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:604) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:288) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:231) 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:94) 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:1651) [...] 2. "from a EntityA left join a.testMap b where index(b)=?" Parameter: <Long> (id of an EntityB) This is really strange: it tries to run the getter of EnityB.id againt a <Long> org.hibernate.PropertyAccessException: could not get a field value by reflection getter of test.EntityB.id at org.hibernate.property.DirectPropertyAccessor$DirectGetter.get(DirectPropertyAccessor.java:58) at org.hibernate.tuple.entity.AbstractEntityTuplizer.getIdentifier(AbstractEntityTuplizer.java:199) at org.hibernate.persister.entity.AbstractEntityPersister.getIdentifier(AbstractEntityPersister.java:3605) [...] Caused by: java.lang.IllegalArgumentException: Can not set long field test.EntityB.id to java.lang.Long at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:146) at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:150) at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:37) at sun.reflect.UnsafeLongFieldAccessorImpl.getLong(UnsafeLongFieldAccessorImpl.java:42) at sun.reflect.UnsafeLongFieldAccessorImpl.get(UnsafeLongFieldAccessorImpl.java:18) at java.lang.reflect.Field.get(Field.java:358) at org.hibernate.property.DirectPropertyAccessor$DirectGetter.get(DirectPropertyAccessor.java:55) ... 67 more 3. "from a EntityA left join a.testMap b where index(b)=?" Parameter: <EntityB> 15:40:24,935 INFO IntegerType:158 - could not bind value '2009219112005957163' to parameter: 1; java.lang.Long cannot be cast to java.lang.Integer java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer at org.hibernate.type.IntegerType.set(IntegerType.java:64) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:154) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:136) at org.hibernate.param.PositionalParameterSpecification.bind(PositionalParameterSpecification.java:68) at org.hibernate.loader.hql.QueryLoader.bindParameterValues(QueryLoader.java:514) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1593) Here it thinks that the index() is of type integer. -- 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
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3743) MININDEX function applied on entity of many-to-many mapped collection yields incorrect SQL

by Stefan Wachter (JIRA)

MININDEX function applied on entity of many-to-many mapped collection yields incorrect SQL ------------------------------------------------------------------------------------------ Key: HHH-3743 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3743 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1, org.hibernate.dialect.DerbyDialect and org.hibernate.dialect.MySQLInnoDBDialect Reporter: Stefan Wachter I have a "t_Person" entity with a "many-to-many" list to a "t_Address" entity: <class entity-name="t_Person" table="F5_T_PERSON" lazy="true"> <id name="_id" column="ID" type="long"> <generator class="native"/> </id> <list lazy="true" cascade="all" name="elemAddress" table="F5_T_PERSON_ELM_ADDRESS"> <key column="OWNER_KEY"/> <list-index column="IDX"/> <many-to-many column="FOREIGN_KEY" entity-name="t_Address"/> </list> </class> <class entity-name="t_Address" table="F5_T_ADDRESS" lazy="true"> <id name="_id" column="ID" type="long"> <generator class="native"/> </id> <property name="attrStreet" type="string"> <column name="A_STREET"/> </property> </class> When I try to retrieve the minimum index of address entities using the following HQL select MININDEX(a) from t_Person as p join p.elemAddress as a incorrect SQL results: select min(t_address2_.IDX) as col_0_0_ from F5_T_PERSON t_person0_ inner join F5_T_PERSON_ELM_ADDRESS elemaddres1_ on t_person0_.ID=elemaddres1_.OWNER_KEY inner join F5_T_ADDRESS t_address2_ on elemaddres1_.FOREIGN_KEY=t_address2_.ID In particular the addressed column "t_address2_.IDX" does not exists. Instead "elemaddres1_.IDX" should be used because the index column is contained in the join table "F5_T_PERSON_ELM_ADDRESS". I assume that the MININDEX function does not consider the case when it is applied to an element of a many-to-many collection. I tested this with the DerbyDialect and the MySQLInnoDBDialect. -- 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
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4661) Properly propagate Query.setLockMode to Hibernate Core

by Emmanuel Bernard (JIRA)

Properly propagate Query.setLockMode to Hibernate Core ------------------------------------------------------ Key: HHH-4661 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4661 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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
10
0 / 0

[Hibernate-JIRA] Created: (EJB-387) The EntityManager.lock() uses the wrong column name when it is passed a sub-type entity from a joined inheritance strategy

by mike wray (JIRA)

The EntityManager.lock() uses the wrong column name when it is passed a sub-type entity from a joined inheritance strategy -------------------------------------------------------------------------------------------------------------------------- Key: EJB-387 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-387 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.GA Environment: Hibernate 3.3.1 Annotations 3.4 Reporter: mike wray Priority: Minor I would expect to see: update SUPER set ROW_VERSION_SEQ=? where SUPER_ID=? and ROW_VERSION_SEQ=? but instead I see: update SUPER set ROW_VERSION_SEQ=? where SUB_ID=? and ROW_VERSION_SEQ=? which throws a org.hibernate.exception.SQLGrammarException: could not retrieve version. This is because column SUB_ID does not exist on table SUPER. -- 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
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3938) One-To-One Filter Applied, Non-Lazy Fetch Problem

by Sandeep Vaid (JIRA)

One-To-One Filter Applied, Non-Lazy Fetch Problem ------------------------------------------------- Key: HHH-3938 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3938 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.1 Reporter: Sandeep Vaid Priority: Critical Suppose i have one-to-one association between Product and ProductBasic. and we have applied filter on ProductBasic Class. I have applied this filter as in Java side we have one-to-one relationship between Product and ProductBasic BUT at database side we have one-to-many relationship between PRODUCT and PRODUCTBASIC. and we apply a condition (STARTTIME < CURRETTIME < ENDTIME) while fetching PRODUCTBASIC, and this will always give me one record out of many. So i have put this condition as filter in ProductBasic class. In current hibernate, one-to-one associations are always non-lazily fetched. Moreover it doesn't apply filter conditions. I understand that it can;t apply filter condition as some filter parameter must be provided at runtime and user may not provide them (as he is not asking for ProductBasic)... Also in this case, proper proxy can't be created as until we apply the filter criteria, we won't get one ProductBasic row (among many).. I think hibernate code should be changed so that if a filter is declared on the associated class (ProductBasic in our case), hibernate should return null for ProductBasic. -- 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-2753) not-found="ignore" causes many-to-one to be always eager

by Fred Gurkov (JIRA)

not-found="ignore" causes many-to-one to be always eager -------------------------------------------------------- Key: HHH-2753 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2753 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1, 3.2.2, 3.1.3 Environment: Tested with 3.1.3, 3.2.2ga, 3.2.4sp1 using Oracle 10g DB. Reporter: Fred Gurkov If not-found property of many-to-one mapping is set to "ignore", the association always gets eagerly initialized regardless of the value of the "lazy" 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
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3828) Criteria: Restriction whith class does not work

by Kai Prünte (JIRA)

Criteria: Restriction whith class does not work ----------------------------------------------- Key: HHH-3828 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3828 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.3.1 Environment: Oracle, HSQLDB Reporter: Kai Prünte The following line does not work: Restrictions.eq("class", Bike.class) because SingleTableEntityPersister.getDiscriminatorSQLValue() returns the discriminator value quoted with single quotes. However JDBC needs the string without quotes. Workaround: Restrictions.eq("class", Bike.class.getName()) This works fine for the default discriminator values Patch in CriteriaQueryTranslator.getTypedValue(Criteria subcriteria, String propertyName, Object value): if(stringValue != null && stringValue.length() > 2 && stringValue.startsWith("'") && stringValue.endsWith("'") ) { // remove the single quotes stringValue = stringValue.substring(1, stringValue.length() - 1); } -- 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
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2009