March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2772) with-clause stopped working

by Ivo Danihelka (JIRA)

with-clause stopped working --------------------------- Key: HHH-2772 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2772 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2 Reporter: Ivo Danihelka The with-clause stopped working in all hibernate versions above 3.2.1 (i.e. 3.2.2+). Before that, it was possible to write HQL: SELECT cat FROM Cat cat LEFT JOIN cat.kittens as kitten WITH kitten.owner=:owner Now the HQL is raising an exception: org.hibernate.hql.ast.InvalidWithClauseException: with clause can only reference columns in the driving table Workaround is to explicitly use primary key (ownerId): SELECT cat FROM Cat cat LEFT JOIN cat.kittens as kitten WITH kitten.owner.ownerId=:ownerId -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-265) Incorrect SQL generated for JPA QL Update statement involving multiple entities

by Alex Savitsky (JIRA)

Incorrect SQL generated for JPA QL Update statement involving multiple entities ------------------------------------------------------------------------------- Key: EJB-265 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-265 Project: Hibernate Entity Manager Type: Bug Versions: 3.2.1 Environment: Hibernate 3.2.2 GA, Oracle 9i Reporter: Alex Savitsky When generating SQL for statements like this: UPDATE Issue i SET i.dueDate = i.dueDate + 10 WHERE i.visit.branch.id = :branchId, an extra comma is generated at the end of table list: update Issue, set DUE_DATE=DUE_DATE+10 where BRANCH_ID=? -- 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, 11 months

7
18
0 / 0

[Hibernate-JIRA] Created: (HHH-2965) When using Criteria.setResultTransformer(CriteriaSpecification.ALIAS_TO_ENTITY_MAP) method aliases need to be optional

by Ittai Zeidman (JIRA)

When using Criteria.setResultTransformer(CriteriaSpecification.ALIAS_TO_ENTITY_MAP) method aliases need to be optional ---------------------------------------------------------------------------------------------------------------------- Key: HHH-2965 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2965 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: 3.2.2 Oracle 10G Reporter: Ittai Zeidman Priority: Critical now when using the CriteriaSpecification- ALIAS_TO_ENTITY_MAP the convertion to map is using the aliases array, if it does not find an alias for the property it is not included in the map. I think that if no alias is defined then the propertyName attribute needs to be assigned as the key for the value in the hashmap. I came across this issue as i have many mapped entities in my system and when using projections i need to use the resultTransformer. this is critical as when using aliases it is duplicated not only to the select clause but to the where clause only which is another open bug (#HB-1331). If one bug is closed then the other can be considered as minor as i can give aliases to every property i need if it does not affect my where clause. -- 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, 11 months

3
6
0 / 0

[Hibernate-JIRA] Created: (JPA-14) OPTIMISTIC_FORCE_INCREMENT is not incrementing version field of non-dirty entities

by Behrang Saeedzadeh (JIRA)

OPTIMISTIC_FORCE_INCREMENT is not incrementing version field of non-dirty entities ---------------------------------------------------------------------------------- Key: JPA-14 URL: http://opensource.atlassian.com/projects/hibernate/browse/JPA-14 Project: Java Persistence API Issue Type: Bug Environment: MySQL 5.1.53 with InnoDB, Hibernate 3.1.6 Final, Java 1.6.0_22 Reporter: Behrang Saeedzadeh According to the JPA 2 spec: {quote} If transaction T1 calls {{lock(entity, LockModeType.OPTIMISTIC_FORCE_INCREMENT)}} on a versioned object, the entity manager must avoid the phenomena P1 and P2 (as with {{LockModeType.OPTIMISTIC}}) and must also force an update (increment) to the entity's version column. A forced version update may be performed immediately, or may be deferred until a flush or commit. If an entity is removed before a deferred version update was to have been applied, the forced version update is omitted. {quote} However, Hibernate is not incrementing the version field when the entity is not altered in the transaction: {code} final EntityManager em = factory.createEntityManager(); em.getTransaction().begin(); VersionedEntity entity = em.find(VersionedEntity.class, id); em.lock(entity, LockModeType.PESSIMISTIC_FORCE_INCREMENT); em.getTransaction().commit(); em.close(); {code} However, the spec says ??must also force an update (increment) to the entity's version column?? and does not give the option to ignore updating the version number if the entity was not dirty. -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6042) To much columns in select queries after creating criteria with join

by Karol Kowalczyk (JIRA)

To much columns in select queries after creating criteria with join ------------------------------------------------------------------- Key: HHH-6042 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6042 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate</artifactId> <version>3.2.6.ga</version> </dependency> Any database Reporter: Karol Kowalczyk Attachments: AbstractEntityJoinWalker.java, Loader.java When I create criteria for any class with any value of property of association f.e.: java code: eventDCriteria = DetachedCriteria.forClass(Event.class); personDCriteria = eventDCriteria.createCriteria("participants"); personDCriteria.add(Expression.eq("age", 41)); List<Event> events=(List<Event>)getHibernateTemplate().findByCriteria(eventDCriteria, 0, 2); class mappings: <class name="Event" table="EVENTS"> <id name="id" column="EVENT_ID"> <generator class="native"/> </id> <property name="date" type="timestamp" column="EVENT_DATE"/> <property name="title"/> <set name="participants" table="PERSON_EVENT" inverse="true"> <key column="EVENT_ID"/> <many-to-many column="PERSON_ID" class="Person"/> </set> </class> <class name="Person" table="PERSON"> <id name="id" column="PERSON_ID"> <generator class="native"/> </id> <property name="age"/> <property name="firstname"/> <property name="lastname"/> <set name="events" table="PERSON_EVENT" > <key column="PERSON_ID"/> <many-to-many column="EVENT_ID" class="Event"/> </set> <set name="emailAddresses" table="PERSON_EMAIL_ADDR" > <key column="PERSON_ID"/> <element type="string" column="EMAIL_ADDR"/> </set> </class> a Hibernate still creates select query f.e.: select e.EVENT_ID, e.EVENT_DATE, e.title, pe.EVENT_ID, pe.PERSON_ID, p.PERSON_ID, p.age, p.firstname, ... from EVENTS e inner join PERSON_EVENT pe on pe.EVENT_ID=e.EVENT_ID inner join PERSON p on p.PERSON_ID=pe.PERSON_ID where p.age=?; Why this hibernates query have UNNECESSARY list of columns: pe.EVENT_ID, pe.PERSON_ID, p.PERSON_ID, p.age, p.firstname, ...? This query is not INDEXONLY for any databases. More EFFECTIVE query is: select e.EVENT_ID, e.EVENT_DATE, e.title from EVENTS e inner join PERSON_EVENT pe on pe.EVENT_ID=e.EVENT_ID inner join PERSON p on p.PERSON_ID=pe.PERSON_ID where p.age=?; A prepared only for my two changes in hibernate: Loader.java and AbstractEntityJoinWalker.java to get more effective selects. -- 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, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-85) Asynchronous incremental optimizer

by Emmanuel Bernard (JIRA)

Asynchronous incremental optimizer ---------------------------------- Key: HSEARCH-85 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-85 Project: Hibernate Search Issue Type: New Feature Components: directory provider Reporter: Emmanuel Bernard Priority: Minor The indexing process itself can be asynchronous, but if not, it would be nice to make the optimization process optionally asynchronous -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-182) Use Directory getLockID() to uniquely identify a directory provider

by Emmanuel Bernard (JIRA)

Use Directory getLockID() to uniquely identify a directory provider ------------------------------------------------------------------- Key: HSEARCH-182 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-182 Project: Hibernate Search Issue Type: Improvement Components: directory provider Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.0 Today the DirectoryProvider needs to implement equals and hashCode so that the underlying Directory is unique. We could delegate that to the directory.getLockID() which seem to fulfill the same contract. Not sure it works well with our lazy initialization strategy though. This needs to be checked 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

12 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-682) DSL cannot handle fieldBridge for @IndexEmbedded fields

by Nick Fenwick (JIRA)

DSL cannot handle fieldBridge for @IndexEmbedded fields ------------------------------------------------------- Key: HSEARCH-682 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-682 Project: Hibernate Search Issue Type: New Feature Components: engine Affects Versions: 3.3.0.Final Environment: Hibernate 3.6.0, HSearch 3.3.0, Mysql 5.1.52. Reporter: Nick Fenwick Discussed in https://forum.hibernate.org/viewtopic.php?f=9&t=1009440, "Re: Correct to use ignoreFieldBridge for "subentity.field" DSL?". I find I have to set ignoreFieldBridge when querying for a field indexed using @IndexEmbedded, i.e.: {code}@Entity class CategoryEntity { @Column(name="lft") @Field(name="left", index=Index.UN_TOKENIZED, store=Store.YES) @FieldBridge(impl=PadNumberBridge.class, params = { @Parameter(name="pad", value="4") } ) private int left; ... same for 'right' ... } @Entity class ItemEntity { @IndexedEmbedded(depth=1) private CategoryEntity category; }{code} results in fields for ItemEntity being stored in the Lucene index like: {code} category.left = 0004 category.right = 0012 {code} To query for these, I cannot do: {code} qb.range().onField("category.left").above(4).createQuery() {code} I get an exception saying it doesn't know what FieldBridge to use for "category.left". Instead, I can do: {code} qb.range().onField("category.left").ignoreFieldBridge().above(4).createQuery() {code} but the 'value' is no longer padded according to the FieldBridge that was specified in CategoryEntity for its 'left' attribute, I have to pass value as e.g. "0004". It would be good to mention this situation in the documentation (5.1.2. "Building a Lucene query with the Hibernate Search query DSL"), at least to specify that it is/isn't supported, so that people attempting this kind of @IndexEmbedded mapping know how to safely build a query for such fields. -- 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, 11 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-551) Using Programamtic API, getters are not inherited

by Chaffotte (JIRA)

Using Programamtic API, getters are not inherited ------------------------------------------------- Key: HSEARCH-551 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-551 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.2.0.Final Environment: hibernate 3.5.1-Final, hsqldb 1.8.0.7 Reporter: Chaffotte Attachments: search2.zip Using Programamtic API, if getters are not defined (overrided) in the child class, the search does not find anything! I had a simple example, remove comments in MySubClass in order to get all tests green! -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-425) AbstractMethodError in WebLogic 10.3.4

by Torsti Töllinen (JIRA)

AbstractMethodError in WebLogic 10.3.4 -------------------------------------- Key: HV-425 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-425 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Beta1 Environment: WebLogic 10.3.4 Hibernate Validator 4.2.0.Beta1 Spring Framework 3.0.5 Reporter: Torsti Töllinen Validation fails on WebLogic 10.3.4 with HV 4.2.0.Beta1. WebLogic has been patched with patch QWG8 (Enable JPA 2.0 support on WebLogic Server. CR/BUG 9923849). With WebLogic version 10.3.3, HV works. java.lang.AbstractMethodError: org.apache.openjpa.persistence.PersistenceProviderImpl.getProviderUtil()Ljavax/persistence/spi/ProviderUtil; at javax.persistence.Persistence$PersistenceUtilImpl.isLoaded(Unknown Source) at org.hibernate.validator.engine.resolver.JPATraversableResolver.isReachable(JPATraversableResolver.java:61) at org.hibernate.validator.engine.resolver.DefaultTraversableResolver.isReachable(DefaultTraversableResolver.java:131) at org.hibernate.validator.engine.resolver.SingleThreadCachedTraversableResolver.isReachable(SingleThreadCachedTraversableResolver.java:46) at org.hibernate.validator.engine.ValidatorImpl.isValidationRequired(ValidatorImpl.java:1126) at org.hibernate.validator.engine.ValidatorImpl.validateConstraint(ValidatorImpl.java:405) at org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForRedefinedDefaultGroup(ValidatorImpl.java:341) at org.hibernate.validator.engine.ValidatorImpl.validateConstraintsForCurrentGroup(ValidatorImpl.java:325) at org.hibernate.validator.engine.ValidatorImpl.validateInContext(ValidatorImpl.java:281) at org.hibernate.validator.engine.ValidatorImpl.validate(ValidatorImpl.java:129) at org.springframework.validation.beanvalidation.SpringValidatorAdapter.validate(SpringValidatorAdapter.java:86) at org.springframework.validation.DataBinder.validate(DataBinder.java:692) at org.springframework.web.bind.annotation.support.HandlerMethodInvoker.doBind(HandlerMethodInvoker.java:807) at org.springframework.web.bind.annotation.support.HandlerMethodInvoker.resolveHandlerArguments(HandlerMethodInvoker.java:359) at org.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:171) at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationMethodHandlerAdapter.java:426) at org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerAdapter.java:414) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:790) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:719) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:644) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:560) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:183) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3717) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) -- 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, 11 months

5
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2011