November 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2594) org.hibernate.criterion.Restrictions.in(?) should break up lists of 1000+ items, Oracle Dialect

by Nathan Silberman (JIRA)

org.hibernate.criterion.Restrictions.in(?) should break up lists of 1000+ items, Oracle Dialect ----------------------------------------------------------------------------------------------- Key: HHH-2594 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2594 Project: Hibernate3 Issue Type: Improvement Components: query-hql Affects Versions: 3.2.0.cr2 Environment: Hibernate 3.2cr2, Oracle DB Reporter: Nathan Silberman Priority: Minor Given a Restriction criteria, if an Array or Collection is passed into the 'in' method, an error is thrown by Oracle complaining that an IN clause must contain at most 1000 items. The Oracle Dialect should be able to segment these items into multiple IN clauses of at most 1000 items each. -- 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

15 years, 10 months

3
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Strong Liu (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123?page=c... ] Strong Liu commented on HHH-1123: --------------------------------- https://jira.jboss.org/jira/browse/JBPAPP-3105 > Cannot put more than 1000 elements in a InExpression > ---------------------------------------------------- > > Key: HHH-1123 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc2, 3.2.0.alpha1 > Environment: Oracle 9i > Reporter: Alexis Seigneurin > Attachments: hibernate-inexpression-oracle-3.2.patch, patch.txt > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The number of elements that we can put in a "in" expression is limited to a certain amount (1000 for Oracle, for instance). When creating a criteria query, the org.hibernate.criterion.InExpression class should split the expression into several smaller ones. > Attached is a patch which splits the expression by slices of 500 elements. For example, if we have 1001 elements to put in the "in" expression, the result would be : > (entity.field in (?, ?, ?...) or entity.field in (?, ?, ?...) or entity.field in (?)) > The surrounding parantheses are useful to avoid problems with other conditions (a "and" condition taking over the one of the "or" conditions). -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-817) Aggregate projection aliases should not be applied to where-clause

by Justin Forder (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-817?page=co... ] Justin Forder commented on HHH-817: ----------------------------------- I said that the "this.property" approach was "(undocumented, so far as I know)". The Hibernate Reference Documentation doesn't mention it (and makes the somewhat misleading statement that "An alias may optionally be assigned to a projection, so that the projected value may be referred to in restrictions or orderings"). However, both "Hibernate in Action" and "Java Persistence with Hibernate" *do* document the use of this.property as an option. (Section 7.3.3 in "Hibernate in Action", and section 15.1.2 in "Java Persistence with Hibernate".) -- Justin Forder > Aggregate projection aliases should not be applied to where-clause > ------------------------------------------------------------------ > > Key: HHH-817 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-817 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Oracle 9.2.0.6, Hibernate 3.0.5, Spring Framework 1.2.2 based application working on Jakarta Tomcat 5.0.28 > Reporter: Michal Jastak > Priority: Minor > Attachments: HHH-817.patch, HHH-817_3.3.2GA_17882.patch > > > following java code: > protected Entity loadEntityLightweight(Serializable entityId) throws DataAccessException { > Criteria criteria = getSession().createCriteria(Entity.class); > ProjectionList projectionList = Projections.projectionList(); > projectionList.add(Property.forName(BaseEntity.PROP_ID), BaseEntity.PROP_ID); > projectionList.add(Property.forName(BaseEntity.PROP_TYPE), BaseEntity.PROP_TYPE); > criteria.setProjection(projectionList); > criteria.add(Restrictions.eq(BaseEntity.PROP_ID, entityId)); > criteria.setResultTransformer(new AliasToBeanResultTransformer(Entity.class)); > return (Entity) criteria.uniqueResult(); > } > generates following SQL query: > select this_.id as y0_, this_.type as y1_ from entities this_ left outer join facilities this_1_ on this_.id=this_1_.id left outer join users this_2_ on this_.id=this_2_.id left outer join addresses address2_ on this_.address_id=address2_.id left outer join entities entity3_ on this_2_.employer_id=entity3_.id left outer join facilities entity3_1_ on entity3_.id=entity3_1_.id left outer join users entity3_2_ on entity3_.id=entity3_2_.id where y0_=? > y0_ = ? expression in where clause is causing a 904 error on Oracle 9: > ORA-00904: "Y0_": invalid identifier > hibernate dialect: org.hibernate.dialect.Oracle9Dialect > mapping for Entity class: > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping default-lazy="false" default-cascade="save-update"> > > <class name="Entity" table="entities" mutable="true"> > <id name="id" type="java.lang.Long" unsaved-value="null"> > <generator class="sequence"> > <param name="sequence">entities_id_seq</param> > </generator> > </id> > <many-to-one name="address" class="Address" column="address_id" /> > ... >  > <joined-subclass name="Facility" table="facilities"> > <key column="id" /> > ... > <set name="users" inverse="true" lazy="true"> > <key column="facility_id" /> > <one-to-many class="User" /> > </set> > </joined-subclass> >  > <joined-subclass name="User" table="users" dynamic-insert="true" dynamic-update="true"> > <key column="id" /> > <many-to-one name="employer" class="Entity" column="employer_id" cascade="none" /> > ... > <set name="userAuthorities" inverse="true" cascade="all-delete-orphan"> > <key column="user_id" /> > <one-to-many class="Authority" /> > </set> > </joined-subclass> > </class> > </hibernate-mapping> -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-817) Aggregate projection aliases should not be applied to where-clause

by Justin Forder (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-817?page=co... ] Justin Forder commented on HHH-817: ----------------------------------- I ran into this today, using Java DB. I tested interactively against Java DB and MySQL to confirm that aliases didn't work in the WHERE clause, then found the MySQL documentation explaining that the SQL standard does not permit the use of aliases here. http://dev.mysql.com/doc/refman/5.0/en/problems-with-alias.html I found this discussed in various threads on the Hibernate User forum. Initially I worked around the problem using an SQL restriction, but then I found the advice here: http://stackoverflow.com/questions/84644/hibernate-query-by-example-and-p... that using "this.property" works. It does, indeed, work for me, but leaves the worry that this (undocumented, so far as I know) behaviour may change in future. I've added a comment to this forum thread: https://forum.hibernate.org/viewtopic.php?f=1&t=988049&p=2421106#p2421106 -- Justin Forder > Aggregate projection aliases should not be applied to where-clause > ------------------------------------------------------------------ > > Key: HHH-817 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-817 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Oracle 9.2.0.6, Hibernate 3.0.5, Spring Framework 1.2.2 based application working on Jakarta Tomcat 5.0.28 > Reporter: Michal Jastak > Priority: Minor > Attachments: HHH-817.patch, HHH-817_3.3.2GA_17882.patch > > > following java code: > protected Entity loadEntityLightweight(Serializable entityId) throws DataAccessException { > Criteria criteria = getSession().createCriteria(Entity.class); > ProjectionList projectionList = Projections.projectionList(); > projectionList.add(Property.forName(BaseEntity.PROP_ID), BaseEntity.PROP_ID); > projectionList.add(Property.forName(BaseEntity.PROP_TYPE), BaseEntity.PROP_TYPE); > criteria.setProjection(projectionList); > criteria.add(Restrictions.eq(BaseEntity.PROP_ID, entityId)); > criteria.setResultTransformer(new AliasToBeanResultTransformer(Entity.class)); > return (Entity) criteria.uniqueResult(); > } > generates following SQL query: > select this_.id as y0_, this_.type as y1_ from entities this_ left outer join facilities this_1_ on this_.id=this_1_.id left outer join users this_2_ on this_.id=this_2_.id left outer join addresses address2_ on this_.address_id=address2_.id left outer join entities entity3_ on this_2_.employer_id=entity3_.id left outer join facilities entity3_1_ on entity3_.id=entity3_1_.id left outer join users entity3_2_ on entity3_.id=entity3_2_.id where y0_=? > y0_ = ? expression in where clause is causing a 904 error on Oracle 9: > ORA-00904: "Y0_": invalid identifier > hibernate dialect: org.hibernate.dialect.Oracle9Dialect > mapping for Entity class: > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping default-lazy="false" default-cascade="save-update"> > > <class name="Entity" table="entities" mutable="true"> > <id name="id" type="java.lang.Long" unsaved-value="null"> > <generator class="sequence"> > <param name="sequence">entities_id_seq</param> > </generator> > </id> > <many-to-one name="address" class="Address" column="address_id" /> > ... >  > <joined-subclass name="Facility" table="facilities"> > <key column="id" /> > ... > <set name="users" inverse="true" lazy="true"> > <key column="facility_id" /> > <one-to-many class="User" /> > </set> > </joined-subclass> >  > <joined-subclass name="User" table="users" dynamic-insert="true" dynamic-update="true"> > <key column="id" /> > <many-to-one name="employer" class="Entity" column="employer_id" cascade="none" /> > ... > <set name="userAuthorities" inverse="true" cascade="all-delete-orphan"> > <key column="user_id" /> > <one-to-many class="Authority" /> > </set> > </joined-subclass> > </class> > </hibernate-mapping> -- 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

15 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4572) check if the connection supports jdbc4 before looking for the createClob method

by Scott Marlow (JIRA)

check if the connection supports jdbc4 before looking for the createClob method ------------------------------------------------------------------------------- Key: HHH-4572 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4572 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2 Reporter: Scott Marlow Priority: Minor Fix For: 3.5 See JBAS-7440 -- 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

15 years, 10 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4573) Minor typo, formatting and cleanup fixes

by Hardy Ferentschik (JIRA)

Minor typo, formatting and cleanup fixes ---------------------------------------- Key: HHH-4573 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4573 Project: Hibernate Core Issue Type: Improvement Components: annotations, core Affects Versions: 3.5.0-Beta-2 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Priority: Trivial Fix For: 3.5 -- 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

15 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3898) Add a flag to disable Nullability.checkNullability() and the exception raised in this case

by Emmanuel Bernard (JIRA)

Add a flag to disable Nullability.checkNullability() and the exception raised in this case ------------------------------------------------------------------------------------------ Key: HHH-3898 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3898 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Fix For: 3.5 Useful when Bean Validation is on as otherwise the checkNullability is applied before BV has time to kick in and messes up the expected exception The default must be true as capt obvious rightly pointed out ;) -- 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

15 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4519) Hibernate/Infinispan integration doesn't property handle Entity/CollectionRegionAccessStrategy evictAll

by Galder Zamarreno (JIRA)

Hibernate/Infinispan integration doesn't property handle Entity/CollectionRegionAccessStrategy evictAll ------------------------------------------------------------------------------------------------------- Key: HHH-4519 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4519 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 3.5 Port HHH-3818 over to the Infinispan 2nd level cache provider. -- 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

15 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4571) Infinispan not properly being built into distribution bundle

by Steve Ebersole (JIRA)

Infinispan not properly being built into distribution bundle ------------------------------------------------------------ Key: HHH-4571 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4571 Project: Hibernate Core Issue Type: Bug Components: build Affects Versions: 3.5.0-Beta-2 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5 The Infinispan integration classes are missing from the consolidated hibernate3.jar and infinispan-core + it's deps are missing from dist lib/ structure -- 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

15 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (EJB-441) nullable=true is ONLY a hint for schema generation, but Hibernate uses it for validation

by Francisco Peredo (JIRA)

nullable=true is ONLY a hint for schema generation, but Hibernate uses it for validation ---------------------------------------------------------------------------------------- Key: EJB-441 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-441 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.2.GA Reporter: Francisco Peredo With the following JPA @Entity (note the @Basic(optional=true), @Column(nullable=false) at the getName method): @Entity public class Customer { private Long id; private String name; @Id @GeneratedValue(strategy=GenerationType.AUTO) public Long getId() { return id; } public void setId(Long id) { this.id = id; } @Basic(optional=true) @Column(nullable=false) public String getName() { return name; } public void setName(String name) { this.name = name; } } And then the following test @Test public void persistCustomerInTransaction() throws Exception { factory = Persistence.createEntityManagerFactory(PERSISTENCE_UNIT_NAME); EntityManager em = factory.createEntityManager(); em.getTransaction().begin(); Customer customer = new Customer(); em.persist(customer);em.getTransaction().commit(); em.close(); } What exception should be the root cause of this problem? According to the spec @Column(nullable=false) is JUST a schema generation hint, and Hibernate should NOT use it for object level validation, so it should crash with a java.sql.SQLException as the root exception, and not with a org.hibernate.PropertyValueException thrown by org.hibernate.engine.Nullability.checkNullability. -- 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

15 years, 10 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2009