May 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5743) Criteria isMember() creates broken SQL in joined queries

by David Momper (JIRA)

Criteria isMember() creates broken SQL in joined queries -------------------------------------------------------- Key: HHH-5743 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5743 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.0, 3.6.1 Environment: Hibernate 3.6.0,3.6.1, all databases Reporter: David Momper Priority: Critical Attachments: Test.zip This problem occurred both when using Oracle, or Derby. I assume it occurs for all databases. I also ran my test case with EclipseLink, and the test passed. A criteria query like this: {quote} CriteriaQuery<Group> groupQuery = cb.createQuery(Group.class); Root<Group> gRoot = groupQuery.from(Group.class); //Get all groups whose leader's name is John, and has a valid visa for given country groupQuery.where(cb.and( cb.like(gRoot.get(Group_.groupLeader) .get(Person_.personName), "%John%"), cb.isMember(country, gRoot.get(Group_.groupLeader) .get(Person_.validVisas) ) )); {quote} produces the following query: {quote} select group0_.GROUP_ID as GROUP1_2_, group0_.LEADER_ID as LEADER3_2_, group0_.GROUP_NAME as GROUP2_2_ from GROUPS group0_, PERSON person1_ where group0_.LEADER_ID=person1_.PERSON_ID and ( person1_.PERSON_NAME like ? ) and ( ? in ( select person1_.PERSON_ID from PERSON person1_ ) ) {quote} The query fails because a (character) country code is being checked for inclusion in a subquery of (int) person ids. The subselect in the above query should be on a country, not a person. I think the whole query should look like this: {quote} select group0_.GROUP_ID as GROUP1_2_, group0_.LEADER_ID as LEADER3_2_, group0_.GROUP_NAME as GROUP2_2_ from GROUPS group0_, PERSON person1_ where group0_.LEADER_ID=person1_.PERSON_ID and ( person1_.PERSON_NAME like ? ) and ( ? in ( select country3_.COUNTRY_CODE from PERSON person1_, PERSON_COUNTRY_VISA validvisas2_, COUNTRY country3_ where group0_.LEADER_ID=person1_.PERSON_ID and person1_.PERSON_ID=validvisas2_.PERSON_ID and validvisas2_.COUNTRY_CODE=country3_.COUNTRY_CODE ) ) {quote} -- 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

12 years, 4 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5130) Add pointers to Infinispan second level cache

by Sanne Grinovero (JIRA)

Add pointers to Infinispan second level cache --------------------------------------------- Key: HHH-5130 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5130 Project: Hibernate Core Issue Type: Improvement Components: caching (L2), documentation Affects Versions: 3.5.1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.5.x Infinispan is not mentioned in the docs, it should be listed at least in the existing table having all caches. -- 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

12 years, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6167) "Mixing nullable" Error Message Correction

by David (JIRA)

"Mixing nullable" Error Message Correction ------------------------------------------ Key: HHH-6167 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6167 Project: Hibernate Core Issue Type: Improvement Components: annotations, core Affects Versions: 3.6.1 Environment: Hibernate 3.6.1.FINAL Reporter: David Priority: Trivial I got the following exception: AnnotationException: Mixing nullable and non nullable columns in a property is not allowed: org.test.domain.PersonlastName Please consider changing it to: property is not allowed: org.test.domain.Person.lastName or property is not allowed: lastName of org.test.domain.Person -- 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

12 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-108) Implement a simpe performance test harness for Bean Validation

by Hardy Ferentschik (JIRA)

Implement a simpe performance test harness for Bean Validation -------------------------------------------------------------- Key: BVAL-108 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-108 Project: Bean Validation Issue Type: Task Components: ri-general Reporter: Hardy Ferentschik JPerf could for example be used. -- 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

12 years, 5 months

1
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2614) Blob Length Set to 255 By Default With Derby DB

by Sean Sylvis (JIRA)

Blob Length Set to 255 By Default With Derby DB ----------------------------------------------- Key: HHH-2614 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2614 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: Apache Derby 10.2.2, Java 1.6.0 Reporter: Sean Sylvis When the (Hibernate) type "blob" is used in an object mapping file and a length is not specified, Hibernate converts this type as "blob (255)" to the Apache Derby database table definition. (This seems to be the same as the conversion behavior of a Java String to "varchar (255).") The same behavior results when using a CustomType that returns a Java SQL Types.BLOB. This is not the behavior I expected. Hibernate converts the same type as simply "blob" (which has a maximum length of 65535 bytes when no length is specified) when using MySQL version 5.0 (http://dev.mysql.com/doc/refman/5.0/en/storage-requirements.html). Furthermore, the Derby specification (http://db.apache.org/derby/docs/10.2/ref/rrefblob.html) states that a blob type without a length value will default to a length of 2M-1 bytes. I could not find a length specification for the Java SQL Blob type (http://java.sun.com/javase/6/docs/api/), but the current default length does seem to conform to other Hibernate type standards. That is, if a length is not specified, the length defaults to the maximum length defined for that type by the database. -- 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

12 years, 5 months

9
13
0 / 0

[Hibernate-JIRA] Created: (HHH-3240) In Derby field type 'text' is converted to CLOB(255)

by Aleksander Rozman (JIRA)

In Derby field type 'text' is converted to CLOB(255) ---------------------------------------------------- Key: HHH-3240 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3240 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.1 Environment: Hibernate 3.1, Derby 10.3.2.1 Reporter: Aleksander Rozman Priority: Blocker When using type 'text' this is incorectly converted to CLOB(255). Derby has several long var char types which could be used instead, but instead it's defaulted to clob(255). I have taken a look at source from 3.1 and 3.2.6 (latest) and this code is still the same... I think that just little fix in DerbyDialect would be enough... I would try this myself but I am currently lacking time and resources. I hope this will be taken care of as soon as it gets... -- 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

12 years, 5 months

7
25
0 / 0

[Hibernate-JIRA] Created: (HHH-5160) Error on binding values prepared statment in many-to-any relation

by wof (JIRA)

Error on binding values prepared statment in many-to-any relation ----------------------------------------------------------------- Key: HHH-5160 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5160 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.3.2 Environment: Tested on Version 3.3.2 and 3.5.1 on Oracle, PostgreSQL and MySQL Reporter: wof A Collection of Entities is defined as a ManyToAny relation, e.g. @ManyToAny(metaColumn=@Column(name="C_OBJECT_TYPE")) @AnyMetaDef(idType="string", metaType="string", metaValues={ @MetaValue(targetEntity=Entity1.class, value="Entity1"), @MetaValue(targetEntity=Entity2.class, value="Entity2") }) @JoinTable(name="T_OBJECTS", joinColumns=@JoinColumn(name="C_OWNER_ID"), inverseJoinColumns=@JoinColumn(name="C_OBJECT_ID") ) private Set<EntityBase> objects = new HashSet<EntityBase>(); Adding to this set works without problems. Removing all elements from the set (i.e. setting the set to null or zero-sized), too. However, when one or more elements are removed from the set with at least one element remaining, an exception is thrown: org.hibernate.exception.GenericJDBCException: could not delete collection rows with the cause being java.sql.SQLException: Parameter index out of range (3 > number of parameters, which is 2). I have narrowed this problem to this: The mapping table consists of 3 columns, C_OWNER_ID, C_OBJECT_TYPE and C_OBJECT_ID. The generated SQL-statement to delete the rows is as folling: DELETE FROM t_objects WHERE c_owner_id=? AND c_object_id=? However, Hibernate (in org.hibernate.typ.AnyType) tries to bind the actual value for c_object_id with index 3 which causes the exception. I guess Hibernate expects c_object_type to be present in the statement. As workaround we changed nullSafeSet in AnyType to: public void nullSafeSet(PreparedStatement st, Object value, int index, boolean[] settable, SessionImplementor session) throws HibernateException, SQLException { Serializable id; String entityName; if (value==null) { id=null; entityName=null; } else { entityName = session.bestGuessEntityName(value); id = ForeignKeys.getEntityIdentifierIfNotUnsaved(entityName, value, session); } // metaType is assumed to be single-column type // <ORIGINAL CODE> /* if ( settable==null || settable[0] ) { metaType.nullSafeSet(st, entityName, index, session); } if (settable==null) { identifierType.nullSafeSet(st, id, index+1, session); } else { boolean[] idsettable = new boolean[ settable.length-1 ]; System.arraycopy(settable, 1, idsettable, 0, idsettable.length); identifierType.nullSafeSet(st, id, index+1, idsettable, session); } */ // </ORIGINAL CODE> // <PATCHED CODE> if ( settable==null || settable[0] ) { metaType.nullSafeSet(st, entityName, index, session); boolean[] idsettable = new boolean[ settable.length-1 ]; System.arraycopy(settable, 1, idsettable, 0, idsettable.length); identifierType.nullSafeSet(st, id, index+1, idsettable, session); } else if (settable==null) { identifierType.nullSafeSet(st, id, index+1, session); } else { boolean[] idsettable = new boolean[ settable.length-1 ]; System.arraycopy(settable, 1, idsettable, 0, idsettable.length); identifierType.nullSafeSet(st, id, index, idsettable, session); } // </PATCHED CODE> } best regards wof -- 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

12 years, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5043) Incorrect handling of hibernate.default_schema in SchemaUpdate

by Vladimir Klyushnikov (JIRA)

Incorrect handling of hibernate.default_schema in SchemaUpdate -------------------------------------------------------------- Key: HHH-5043 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5043 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5.0-CR-2 Environment: Hibernate Core 3.5.0-CR-2, Oracle 10.2 Reporter: Vladimir Klyushnikov Attachments: cfg.patch While HHH-735 fixes default_schema handling in general, it still has a bug. When SchemaUpdate reads foreign keys metainfo is doesn't honor default_schema and default_catalog settings. The fix is simple and patch is attached. -- 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

12 years, 5 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HV-411) Move LazyValidatorFactory into org.hibernate.validator.engine

by Hardy Ferentschik (JIRA)

Move LazyValidatorFactory into org.hibernate.validator.engine ------------------------------------------------------------- Key: HV-411 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-411 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.1.0.Final Reporter: Hardy Ferentschik Fix For: 4.x This class does not belong into the util package and also created an unnecessary package cycle. According to the classes docs it is used in JBoss AS 6. A move must be synced with the AS. -- 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

12 years, 5 months

2
7
0 / 0

[Hibernate-JIRA] Created: (ANN-728) @NaturalId doesn't work with @Embeddable/@Embedded

by Kenny MacLeod (JIRA)

@NaturalId doesn't work with @Embeddable/@Embedded -------------------------------------------------- Key: ANN-728 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-728 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Reporter: Kenny MacLeod Attachments: BugTestCase.java If I try to annotate an @Entity's field with @NaturalId, and that field happens to be @Embedded or @Embeddable, then hibernate barfs with org.hibernate.MappingException: Unable to find logical column name from physical name component in table BugTestCase$MyEntity at org.hibernate.cfg.Mappings.getLogicalColumnName(Mappings.java:514) at org.hibernate.cfg.IndexOrUniqueKeySecondPass.doSecondPass(IndexOrUniqueKeySecondPass.java:61) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1136) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:324) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:859) See attached unit test as a demonstration. Surely this is not an exotic scenario? Tested with Hibernate Core 3.2.6-GA -- 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

12 years, 5 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2011