December 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2381) Criteria API : Order by Native SQL

by Sami Dalouche (JIRA)

Criteria API : Order by Native SQL ----------------------------------- Key: HHH-2381 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2381 Project: Hibernate3 Type: Improvement Components: query-criteria Reporter: Sami Dalouche Hi, It would be nice to be able to specify the ORDER BY clause using Native SQL. (It is currently doable by subclassing the Order class, but some nice solution would allow the order to specify attributes on another table..) Let's take a simple example : I have a distance("attribute", geometry) function, that is of course, proprietary. I am quering table A, which I can join to table B to get the "attribute", on which I want to apply my distance() function. If I create my own Order subclass, and addOrder on the criteria, the distance("attribute, geometry) is going to refer to the main criteria's class mapping. So, something like addOrder("objectpath.joined", new MyOrder(...)); would be perfect. What do you think ? Regards, Sami Dalouche -- 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

13 years, 4 months

4
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2952) Support for referencing non-root entities in Criteria SQL expressions

by Jacob Gyllenstierna (JIRA)

Support for referencing non-root entities in Criteria SQL expressions --------------------------------------------------------------------- Key: HHH-2952 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2952 Project: Hibernate3 Issue Type: Improvement Components: query-criteria Affects Versions: 3.2.2 Environment: Java 5, MySQL 5.0, Eclipse 3.2 Reporter: Jacob Gyllenstierna It would be very helpful to be able to reference non-root entities in Criteria SQL restrictions and projections using placeholders similar to {alias}. A very simple but uninteresting example: criteria.createAlias("group", "g"); criteria.add(Restrictions.sqlRestriction("{g}.id=:groupId")); -- 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

13 years, 4 months

8
22
0 / 0

[Hibernate-JIRA] Created: (HHH-2045) in () result in "unexpected end of subtree"

by Max Rydahl Andersen (JIRA)

in () result in "unexpected end of subtree" -------------------------------------------- Key: HHH-2045 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2045 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Reporter: Max Rydahl Andersen "in ()" is a valid sql construct and works with previous versions of Hibernate. The new parser throws an "unexpected end of subtree". example: from Animal an where an.id in () or from Animal an where an.id in (:list) and input list is an empty list. Is this the behavior we want from now on or ? -- 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

13 years, 4 months

10
18
0 / 0

[Hibernate-JIRA] Created: (HHH-2054) Persistent wrapper collections should support generics

by Daniel Kandel (JIRA)

Persistent wrapper collections should support generics ------------------------------------------------------ Key: HHH-2054 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2054 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr2 Reporter: Daniel Kandel Hibernate persistent wrapper collections - classes that extend AbstractPersistentCollection and implement map, set or list (like PersistentSet and PersistentList), should support generics (PersistentSet<String>, PersistentMap<Integer, String>). In order to create a custom collection, one must extend one of these classes, but then the new collection cannot support generics. -- 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

13 years, 4 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HBX-1100) hbm2dll creates FK constraint names that are too large for taget database dialect

by Duncan Keysell (JIRA)

hbm2dll creates FK constraint names that are too large for taget database dialect --------------------------------------------------------------------------------- Key: HBX-1100 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1100 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.4 Beta1 Reporter: Duncan Keysell When hbm2dll creates FK constraint names, it does so without following database resrictions. As hbm2dll knows it is using the Oracle10gDialect then it should not attempt to create FK constraint names that have more than 30 characters. With union-subclass mapping the pattern used by hbm2dll is to give a FK constraint an 18 character name on the class that directly has the association requiring the FK. If that class is subclassed the FK constraint added to the tables of the subclasses has 18+8n characters. Where n is the level of subclassing. Only two levels of subclassing are required before the constraint name exceeds 30 characters as below. I know it is possible to configure the initial name used for constraints using the foreign-key attribute in the mapping. However if I set that to 1 character then I still have a problem when 1 + 4*8 = 33. Therefore even using the foreign-key attribute I can only get 3 levels of subclassing. Shouldn't the algorithm to create FK names be aware of the 30 character limit, i.e be dialect aware. Couldn't it simply create a hashcode of the hashcode it currently creates and limit it to 30 characters (including the 'FK'). In the example below constraints of the lengths shown get added to each table for the many-to-one mapping with name="requestedNE": Class IACEndpointConfigElement (FK4C10C05A145A4B50) 18 chars IInterfaceConfigElement (FK4C10C05A145A4B50b6728c4a) 18 + 8 = 26 chars IFRvcConfigElement (FK4C10C05A145A4B50b6728c4ace4cc838) 18 + 8 + 8 = 34 chars ERROR Hibernate version: 3.2.2 Mapping documents: <class name="productSpecific.advancedAppInterfaces.attachmentCircuitService.IACEndpointConfigElement" table="IACEndpointConfigElement" abstract="true"> <many-to-one name="requestedNE" class="productSpecific.advancedAppInterfaces.attachmentCircuitService.IACServiceNEAssignmentConfigElement" column="requestedNE_ID" foreign-key="none" not-found="ignore" /> <union-subclass name="productSpecific.advancedAppInterfaces.attachmentCircuitService.IInterfaceConfigElement" table="IInterfaceConfigElement" abstract="false"> <union-subclass name="productSpecific.advancedAppInterfaces.attachmentCircuitService.IFRvcConfigElement" table="IFRvcConfigElement" abstract="false"> </union-subclass> </union-subclass> </class Code between sessionFactory.openSession() and session.close(): N/A Full stack trace of any exception that occurs: N/A Name and version of the database you are using: Oracle 10g The generated SQL (show_sql=true): [hibernatetool] 2008-11-26 09:56:40,000 DEBUG SchemaExport:303 - [hibernatetool] create table developer.IFRvcConfigElement ( [hibernatetool] INSTANCEID number(19,0) not null, [hibernatetool] oid varchar2(2048 char) not null, [hibernatetool] ReferenceKey varchar2(2048 char), [hibernatetool] InstanceName varchar2(255 char), [hibernatetool] InstanceDescription varchar2(255 char), [hibernatetool] requestedNE_ID number(19,0), [hibernatetool] ProtocolIFType number(10,0), [hibernatetool] InterfaceEncapType number(10,0), [hibernatetool] Dlci number(10,0), [hibernatetool] primary key (INSTANCEID) [hibernatetool] ); [hibernatetool] alter table developer.IFRvcConfigElement [hibernatetool] add constraint FK4C10C05A145A4B50b6728c4ace4cc838 [hibernatetool] foreign key (requestedNE_ID) [hibernatetool] references developer.IACSrvcNEAssgnmntCnfgElmnt; [hibernatetool] 2008-11-26 10:00:18,515 ERROR SchemaExport:274 - Unsuccessful: alter table developer.IFRvcConfigElement add constraint FK4C10C05A145A4B50b6728c4ace4cc838 foreign key (requestedNE_ID) references developer.IACSrvcNEAssgnmntCnfgElmnt [hibernatetool] 2008-11-26 10:00:18,515 ERROR SchemaExport:275 - ORA-00972: identifier is too long Debug level Hibernate log excerpt: DEBUG Problems with Session and transaction handling? N/A -- 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

13 years, 4 months

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-469) bulk update with native sql queries

by Amir Pashazadeh (JIRA)

bulk update with native sql queries ----------------------------------- Key: ANN-469 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-469 Project: Hibernate Annotations Type: Improvement Components: binder Versions: 3.2.0.ga Reporter: Amir Pashazadeh Priority: Critical Hibernate Annotations 3.2 does not support bulk update/deletes using native queries, if I have something like: @NamedNativeQuery(name = "testQuery", query = "delete from tb_test where id = ?") in one of my entities, there will be following exception during build of SessionFactory : Exception in thread "main" org.hibernate.cfg.NotYetImplementedException: Pure native scalar queries are not yet supported at org.hibernate.cfg.annotations.QueryBinder.bindNativeQuery(QueryBinder.java:118) at org.hibernate.cfg.annotations.QueryBinder.bindNativeQueries(QueryBinder.java:197) at org.hibernate.cfg.AnnotationBinder.bindQueries(AnnotationBinder.java:281) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:404) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:452) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:268) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1210) ------ I made a mistake and I reported this issue as HHH-2147 as an issue about Hibernate core! :( -- 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

13 years, 4 months

11
16
0 / 0

[Hibernate-JIRA] Created: (HHH-2403) Support multi-line import.sql files

by Christian Bauer (JIRA)

Support multi-line import.sql files ----------------------------------- Key: HHH-2403 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2403 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.2 Reporter: Christian Bauer I leave this as Major, because it most likely breaks all existing import.sql's. The statement delimiter in import.sql is currently a newline. We need to change that to: - delimiter is semicolon, so users can copy/paste stuff from and to SQL consoles - newline is a real newline, allows users to enter newlines into larger text columns without a 5000 character wide line -- 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

13 years, 4 months

11
27
0 / 0

[Hibernate-JIRA] Created: (HHH-2171) Transaction Rollback Problem in GA due to jboss cache alpha dependency

by bhumika thakkar (JIRA)

Transaction Rollback Problem in GA due to jboss cache alpha dependency ---------------------------------------------------------------------- Key: HHH-2171 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2171 Project: Hibernate3 Type: Bug Components: build Versions: 3.2.0.ga Reporter: bhumika thakkar We upgraded to Hibernate GA, and started getting Transaction Rolloback Exception. GA release is distributed with JBoss cache alpha quality dependency. Upgrading to the current production release of it fixes the issue. Stack trace: org.jboss.cache.interceptors.TxInterceptor.runRollbackPhase Rollback had a problem java.lang.IllegalStateException: local transaction Transaction[] transaction does not match running tx null at org.jboss.cache.interceptors.TxInterceptor.handleCommitRollback(TxInterc eptor.java:616) at org.jboss.cache.interceptors.TxInterceptor.runRollbackPhase(TxIntercepto r.java:696) at org.jboss.cache.interceptors.TxInterceptor$RemoteSynchronizationHandler. afterCompletion(TxInterceptor.java:947) at org.jboss.cache.interceptors.OrderedSynchronizationHandler.afterCompleti on(OrderedSynchronizationHandler.java:80) at com.caucho.transaction.TransactionImpl.callAfterCompletion(TransactionIm pl.java:893) at com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:713) at com.caucho.transaction.TransactionManagerImpl.commit(TransactionManagerI mpl.java:263) at com.caucho.jca.UserTransactionImpl.commit(UserTransactionImpl.java:411) at com.caucho.jca.UserTransactionProxy.commit(UserTransactionProxy.java:142 ) at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTr ansactionManager.java:787) at org.springframework.transaction.support.AbstractPlatformTransactionManag er.processCommit(AbstractPlatformTransactionManager.java:500) at org.springframework.transaction.support.AbstractPlatformTransactionManag er.commit(AbstractPlatformTransactionManager.java:473) at org.springframework.transaction.interceptor.TransactionAspectSupport.doC ommitTransactionAfterReturning(TransactionAspectSupport.java:267) at org.springframework.transaction.interceptor.TransactionInterceptor.invok e(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Ref lectiveMethodInvocation.java:170) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAo pProxy.java:176) at $Proxy119.executeCallback(Unknown Source) ... -- 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

13 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3235) Re-assembling entity from clustered JBoss Cache may fail with "argument type mismatch"

by Peter Johnson (JIRA)

Re-assembling entity from clustered JBoss Cache may fail with "argument type mismatch" -------------------------------------------------------------------------------------- Key: HHH-3235 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3235 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Environment: 3.2.4.sp1 in JBoss 4.2.2 GA, with MySQL 5.0.32 ( JBoss log also reports Hibernate EntityManager 3.2.1.GA, Hibernate Annotations 3.2.1.GA ) Reporter: Peter Johnson My application is configured for Hibernate to use the JBoss Cache TreeCache and I have the application deployed in a JBoss cluster. For some reason, with the latest deployment of my software (probably coincidentally when I moved to JBoss Seam 2.0) I started running into a problem where I would get an IllegalArgumentException when Hibernate pulled entities out of the replicated instance of the cache. It looks like when Hibernate pulls values out of the cache and attempts to re-assemble an entity from a CacheEntry, it tries to put a value into the wrong property of the entity. My entity has several int fields and a single String field. The full stack trace is at the end of this description. Looking briefly at the source for CacheEntry, it appears to store the entity's property values in an array, and when it later obtains the list of properties (from entity metadata) in order to re-assemble the entity, it assumes the order will match the order of the value array in the CacheEntry. So in my case, either the property values must be in a different order in the second JVM's cache instance, or the list of properties in the entity metadata must be different. Looking at the printDetails of the EJB3EntityTreeCache MBean in both JBoss instances, the CacheEntries seem to have the values in the same order--at least it prints the values in the same order on each instance. This leads me to believe that the entity metadata identifies the properties in a different order in the two JVMs. (I don't have definitive proof, however). Setting hibernate.cache.use_structured_entries to "true" works around the problem. 2008-04-07 14:52:07,590 ERROR [org.hibernate.property.BasicPropertyAccessor] IllegalArgumentException in class: com.zattoo.channelserver.entity.permission.AbstractPermissionRule, setter method of property: rule 2008-04-07 14:52:07,590 ERROR [org.hibernate.property.BasicPropertyAccessor] expected type: java.lang.String, actual value: java.lang.Integer 2008-04-07 14:52:07,591 INFO [org.hibernate.event.def.DefaultLoadEventListener] Error performing load command org.hibernate.PropertyAccessException: IllegalArgumentException occurred while calling setter of com.zattoo.channelserver.entity.permission.AbstractPermissionRule.rule at org.hibernate.property.BasicPropertyAccessor$BasicSetter.set(BasicPropertyAccessor.java:104) at org.hibernate.tuple.entity.AbstractEntityTuplizer.setPropertyValues(AbstractEntityTuplizer.java:337) at org.hibernate.tuple.entity.PojoEntityTuplizer.setPropertyValues(PojoEntityTuplizer.java:200) at org.hibernate.persister.entity.AbstractEntityPersister.setPropertyValues(AbstractEntityPersister.java:3566) at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:116) at org.hibernate.cache.entry.CacheEntry.assemble(CacheEntry.java:82) at org.hibernate.event.def.DefaultLoadEventListener.assembleCacheEntry(DefaultLoadEventListener.java:553) at org.hibernate.event.def.DefaultLoadEventListener.loadFromSecondLevelCache(DefaultLoadEventListener.java:508) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:357) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:846) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:557) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:196) at org.hibernate.collection.PersistentBag.initializeFromCache(PersistentBag.java:141) at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1716) at org.hibernate.collection.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:454) at org.hibernate.engine.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:797) at org.hibernate.event.def.DefaultLoadEventListener.assembleCacheEntry(DefaultLoadEventListener.java:580) at org.hibernate.event.def.DefaultLoadEventListener.loadFromSecondLevelCache(DefaultLoadEventListener.java:508) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:357) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:846) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:557) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:196) at org.hibernate.collection.PersistentBag.initializeFromCache(PersistentBag.java:141) at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1716) at org.hibernate.collection.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:454) at org.hibernate.Hibernate.initialize(Hibernate.java:309) at com.zattoo.channelserver.session.ChannelProviderBean.getAllPartitions(ChannelProviderBean.java:127) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:44) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:101) at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:240) at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:210) at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84) at $Proxy161.getAllPartitions(Unknown Source) at com.zattoo.channelserver.service.ChannelCacheService.loadPartitionCache(ChannelCacheService.java:136) at com.zattoo.channelserver.service.ChannelCacheService.getAllPartitions(ChannelCacheService.java:155) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:44) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:101) at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.service.ServiceContainer.localInvoke(ServiceContainer.java:329) at org.jboss.ejb3.service.ServiceContainer.localInvoke(ServiceContainer.java:294) at org.jboss.ejb3.service.ServiceMBeanDelegate.getAttribute(ServiceMBeanDelegate.java:139) at org.jboss.mx.server.RawDynamicInvoker.getAttribute(RawDynamicInvoker.java:117) at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:556) at org.jboss.jmx.adaptor.control.Server.getMBeanAttributeResultInfo(Server.java:144) at org.apache.jsp.inspectMBean_jsp._jspService(inspectMBean_jsp.java:185) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:373) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:336) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.inspectMBean(HtmlAdaptorServlet.java:204) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:96) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doGet(HtmlAdaptorServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:856) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:566) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1508) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.IllegalArgumentException: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.property.BasicPropertyAccessor$BasicSetter.set(BasicPropertyAccessor.java:42) ... 155 more -- 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

13 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-376) EntityManager.createQuery does not recognize COUNT CASE statement

by Mark Plutowski (JIRA)

EntityManager.createQuery does not recognize COUNT CASE statement ----------------------------------------------------------------- Key: EJB-376 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-376 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.4.0.CR2, 3.3.1.GA Environment: Tested with both Hibernate 3.2.5.ga and Hibernate 3.3.0.CR2, Postgres 8.1, Postgres 8.2, Linux Ubuntu. Reporter: Mark Plutowski I searched the Hibernate forums and did not find mention of this issue or one that was closely related. I also posted this to the Hibernate Users forum, and did not receive any replies recognizing the bug or stating that it has been resolved or has a workaround. To summarize, EntityManager.createQuery does not recognize SQL related to applying a COUNT to a CASE, whereas it does correctly run SQL that applies a SUM to a CASE. More detail follows. --- Summary Overview --- EntityManager.createQuery runs a SELECT query containing the following HQL/JQL snippet runs correctly: " SUM ( CASE WHEN (cs.serveTs BETWEEN :beginTs AND :endTs ) THEN 1 ELSE 0 END ) " However, the following do not work: " COUNT ( DISTINCT CASE WHEN (cs.serveTs BETWEEN :beginTs AND :endTs ) THEN cs.componentId ELSE NULL END ) " " COUNT ( DISTINCT (CASE WHEN (cs.serveTs BETWEEN :beginTs AND :endTs ) THEN cs.componentId ELSE NULL END ) ) " " COUNT ( CASE WHEN (cs.serveTs BETWEEN :beginTs AND :endTs ) THEN cs.componentId ELSE NULL END ) " The first two statements run and return correct results when translated to SQL and run against the Postgresql database in PgAdmin. Here's the exception thrown when using COUNT ( DISTINCT CASE WHEN 101976 [main] ERROR org.hibernate.hql.PARSER - line 1:93: unexpected token: CASE 101977 [main] ERROR org.hibernate.hql.PARSER - line 1:98: unexpected token: WHEN Here's the exception thrown when the extra parenthesis is added to give COUNT ( DISTINCT (CASE WHEN 85587 [main] ERROR org.hibernate.hql.PARSER - line 1:93: unexpected token: ( 85588 [main] ERROR org.hibernate.hql.PARSER - line 1:99: unexpected token: WHEN --- Additional Detail --- Here is the complete SQL for the COUNT (DISTINCT (CASE use case: String queryString = "Select c.id.pubId, c.id.clipId, c.duration, " + "count(distinct s.slotId) , " + " COUNT ( DISTINCT (CASE WHEN (cs.serveTs BETWEEN :beginTs AND :endTs ) THEN cs.componentId ELSE NULL END ) ) " + "from CmClip c " + "join c.cmClipSlots s " + "left outer join c.csComponents cs " + "where (s.adSizeX * c.width) >= :adWidth " + "and (s.adSizeY * c.height) >= :adHeight " + "and (c.isQaDone = true or c.isQaDone is null) " + "and c.isEnabled = true " + "group by c.id.pubId, c.id.clipId, c.duration " + "order by " + orderByCol; This results in the following exception: 85587 [main] ERROR org.hibernate.hql.PARSER - line 1:93: unexpected token: ( 85588 [main] ERROR org.hibernate.hql.PARSER - line 1:99: unexpected token: WHEN Here is the SQL for the SUM CASE sql snippet that does run and return correct results: String queryString = "Select c.id.pubId, c.id.clipId, c.duration, " + "count(distinct s.slotId) , " + " SUM ( CASE WHEN (cs.serveTs BETWEEN :beginTs AND :endTs ) THEN 1 ELSE 0 END ) " + "from CmClip c " + "join c.cmClipSlots s " + "left outer join c.csComponents cs " + "where (s.adSizeX * c.width) >= :adWidth " + "and (s.adSizeY * c.height) >= :adHeight " + "and (c.isQaDone = true or c.isQaDone is null) " + "and c.isEnabled = true " + "group by c.id.pubId, c.id.clipId, c.duration " + "order by " + orderByCol; Here is the code snippet that performs the transaction: float roFactor = (float) 0.5; transactionMgr.begin(); List<Object[]> result = entityMgr.createQuery(queryString) .setParameter("adWidth", (widthF-roFactor)). setParameter("adHeight", (heightF-roFactor)) .setParameter("beginTs", beginTs, javax.persistence.TemporalType.TIMESTAMP) .setParameter("endTs", endTs, javax.persistence.TemporalType.TIMESTAMP) .getResultList(); transactionMgr.commit(); The fact that "SUM (CASE" is parsed and run correctly, whereas "COUNT (CASE" throws an exception seems to indicate a bug. I replicated this using both (Hibernate 3.2.5.ga with EntityManager 3.3.1.GA) and (Hibernate 3.3.0.CR2 with EntityManager 3.4.0.CR2). -- 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

13 years, 4 months

8
13
0 / 0

[Hibernate-JIRA] Created: (HHH-2951) Restrictions.eq when passed null, should create a NullRestriction

by David Sheldon (JIRA)

Restrictions.eq when passed null, should create a NullRestriction ----------------------------------------------------------------- Key: HHH-2951 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2951 Project: Hibernate3 Issue Type: Improvement Components: query-criteria Affects Versions: 3.2.1 Reporter: David Sheldon Priority: Trivial If you create a Restriction using eq, and pass null to it, then the generated SQL is "where foo = null", which always returns false. The programmer will almost certainly have intended to get "where foo is null". Ideally, we could change: public static SimpleExpression eq(String propertyName, Object value) { return new SimpleExpression(propertyName, value, "="); } to public static SimpleExpression eq(String propertyName, Object value) { if (value == null) { return isNull(propertyName); } else { return new SimpleExpression(propertyName, value, "="); } } Unforunately that wont work, as isNull doesn't return a SimpleExpression. -- 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

13 years, 4 months

8
13
0 / 0

[Hibernate-JIRA] Created: (HHH-3238) impossible to get the rowcount for a criteria that has projections

by hbMailingList (JIRA)

impossible to get the rowcount for a criteria that has projections ------------------------------------------------------------------ Key: HHH-3238 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3238 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: hibernate 3.2.6, oracle 10g Reporter: hbMailingList Projections.rowCount correctly returns the NUMBER_OF_ROWS for the criteria's resultset. However if the criteria already has a projection then rowcount no longer returns the NUMBER_OF_ROWS in the result set. For example: Criteria c=session.CreateCriteria(Cat.class); ProjectionList pl = ...; .... pl.add(Projections.groupProperty("color")); pl.add(Projections.rowCount()); c.setProjections(pl); c.list(); will result in the following query: select color, count(*) from cats group by color I would expect it to result in: select count(*) from (select color from cats group by color) after all if I wanted the count by color I could have simply done: Projections.count(...) I really need this feature for my project...if you don't think this will make the release, would you please give me a hint and I'll submit a patch. Thanks for all the hard work. -- 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

13 years, 4 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2218) java.util.ConcurrentModificationException at org.hibernate.pretty.Printer.toString(Printer.java:90)

by rm (JIRA)

java.util.ConcurrentModificationException at org.hibernate.pretty.Printer.toString(Printer.java:90) --------------------------------------------------------------------------------------------------- Key: HHH-2218 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2218 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Hibernate 3.1.3, spring 2.1.8 on Jboss 4.0.2 with Oracle 10g Reporter: rm Similar issues have been logged since May 2005 and have been marked as 'Fixed' by Gavin especially for Session.toString() related cases. However, I am also facing similar issues in Printer.toString()... The saving grace is that when I set the debug level to INFO, the problem goes away... Am copy/pasting the relevent stacktrace...I have also debugged this on eclipse and the exact location is the call to "new Printer(....)" in AbstractFlushingEventListener.java java.util.ConcurrentModificationException 10:07:28,421 INFO [STDOUT] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:787) 10:07:28,421 INFO [STDOUT] at java.util.HashMap$ValueIterator.next(HashMap.java:817) 10:07:28,421 INFO [STDOUT] at org.hibernate.pretty.Printer.toString(Printer.java:90) 10:07:28,421 INFO [STDOUT] at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:97) 10:07:28,421 INFO [STDOUT] at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:954) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1099) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) PS: This is my first attempt at logging issues at JIRA. Kindly point out any deficiencies or irregularities in this attempt. -- 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

13 years, 4 months

6
9
0 / 0

[Hibernate-JIRA] Created: (ANN-784) MapBinder.createFormulatedValue() does not honor DB schema name when creating query

by Sven Panko (JIRA)

MapBinder.createFormulatedValue() does not honor DB schema name when creating query ----------------------------------------------------------------------------------- Key: ANN-784 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-784 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Environment: Hibernate 3.3.0.SP1, PostgresQL 8.3 Reporter: Sven Panko I detected a problem with a ManyToMany mapping using a Map in the following setup: @Entity @Table(name = "entitya", schema = "myschema") class EntityA { ... @ManyToMany(cascade = { CascadeType.PERSIST, CascadeType.MERGE }) @MapKey(name = "identifier") @JoinTable(name = "entitya_entityb", schema="myschema", joinColumns = @JoinColumn(name = "entitya_pk"), inverseJoinColumns = @JoinColumn(name = "entityb_pk")) @Cascade( { org.hibernate.annotations.CascadeType.SAVE_UPDATE, org.hibernate.annotations.CascadeType.DELETE_ORPHAN }) @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) private Map<String, EntityB> entityBMap = new HashMap<String, EntityB>(); } @Entity @Table(name = "entityb", schema = "myschema") class EntityB { ... } The SQL generated to load the entityBMap collection contains a subquery in the select clause, which looks like this: select a8.identifier from entityb a8 where a8.pk=entityb0_.entityb_pk (entityb0_.entityb_pk comes from the outer select clause) The problem here is, that entityb in the from clause is not prepended by the schema name "myschema" (the outer query is correctly doing this in the join clause, however). I tracked this down to the createFormulatedValue() method in the MapBinder class; the responsible code snippet is contained in lines 292 - 296: StringBuilder fromAndWhereSb = new StringBuilder( " from " ) .append( associatedClass.getTable().getName() ) //.append(" as ") //Oracle doesn't support it in subqueries .append( " " ) .append( alias ).append( " where " ); associatedClass.getTable().getName() does not return the fully qualified table name, so I think this should look something like this: StringBuilder fromAndWhereSb = new StringBuilder( " from " ); if (associatedClass.getTable().getSchema() != null) { fromAndWhereSb.append(associatedClass.getTable().getSchema()).append('.'); } fromAndWhereSb.append( associatedClass.getTable().getName() ) //.append(" as ") //Oracle doesn't support it in subqueries .append( " " ) .append( alias ).append( " where " ); -- 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

13 years, 4 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3502) getIdentifierMethod of BasicLazyInitializer does not match if method invoked through an interface with different return type

by Sean Bridges (JIRA)

getIdentifierMethod of BasicLazyInitializer does not match if method invoked through an interface with different return type ---------------------------------------------------------------------------------------------------------------------------- Key: HHH-3502 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3502 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Reporter: Sean Bridges Priority: Minor I have an entity interface, public interface IEntity { public Object getId(); } and I have an entity, say User that implements this interface with an id method @Id public Long getId() { return id; } I can call getId() on an uninitialized proxy with, user.getId() however, if I call getId() in this way, ((IEntity) user)).getId() I get org.hibernate.LazyInitializationException: could not initialize proxy - no Session Looking at the code, BasicLazyInitializer has these lines, else if ( isUninitialized() && method.equals(getIdentifierMethod) ) { return getIdentifier(); } the method.equals(getIdentifierMethod) returns false. The methods are not equal() because they have different return types (this is allowed in 1.5 with covariant return types). Hibernate should not use Method.equals(), but should instead use the code below (modified from Method.equals(Object)), public boolean equalsIgnoringReturnType(Method m1, Method m2) { if ((m1.getDeclaringClass() != m2.getDeclaringClass()) { return false; } if (m1.getName() != m2.getName()) { return false; } Class[] params1 = m1.getParameterTypes(); Class[] params2 = m2.getParameterTypes(); if (params1.length != params2.length) { return false; } for (int i = 0; i < params1.length; i++) { if (params1[i] != params2[i]) return false; } return true; } -- 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

13 years, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2744) QueryException raised for valid SQL query - problems with aliases parsing

by Michal Jastak (JIRA)

QueryException raised for valid SQL query - problems with aliases parsing ------------------------------------------------------------------------- Key: HHH-2744 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2744 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.1 Environment: Tomcat 5.5, Hibernate Annotations 3.3.0 ga Reporter: Michal Jastak SQLQuery parser dose not parse queries correctly. Trying to invoke: session.createSQLQuery("select foo from bar where foo like '{%'"); ends with: rg.hibernate.QueryException: Unmatched braces for alias path [select foo from bar where foo like '{%'] at org.hibernate.loader.custom.sql.SQLQueryParser.substituteBrackets(SQLQueryParser.java:74) at org.hibernate.loader.custom.sql.SQLQueryParser.process(SQLQueryParser.java:51) at org.hibernate.loader.custom.sql.SQLCustomQuery.<init>(SQLCustomQuery.java:110) at org.hibernate.engine.query.NativeSQLQueryPlan.<init>(NativeSQLQueryPlan.java:43) at org.hibernate.engine.query.QueryPlanCache.getNativeSQLQueryPlan(QueryPlanCache.java:114) at org.hibernate.impl.AbstractSessionImpl.getNativeSQLQueryPlan(AbstractSessionImpl.java:137) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:152) -- 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

13 years, 5 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2647) Problems with OR parenthesis in HQL

by Dennis Fleurbaaij (JIRA)

Problems with OR parenthesis in HQL ----------------------------------- Key: HHH-2647 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2647 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.1 Environment: Hibernate 3.2.1, postgresql 8.2, jboss 5 embedded beta 2 Reporter: Dennis Fleurbaaij Given the following (part) of a query in HQL (where 1 to 6 are comparisons of different types (=, <=, is null), but irrelevant for the problem posted here ): AND ( ( 1 AND 2 ) OR ( 3 AND 4 ) OR ( 5 AND 6 ) ) will be balanced to: and ( ( 1 ) and 2 or 3 and ( 4 ) or 5 and 6 ) -- 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

13 years, 5 months

12
23
0 / 0

[Hibernate-JIRA] Created: (HHH-2031) Add functions to Dialect that can disable use of schema and catalog parts -- for HSQLDB support

by Brian Holmes (JIRA)

Add functions to Dialect that can disable use of schema and catalog parts -- for HSQLDB support ----------------------------------------------------------------------------------------------- Key: HHH-2031 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2031 Project: Hibernate3 Type: Patch Components: core Versions: 3.1.3 Environment: This patch is against r9668 of /tags/v313/Hibernate3. Reporter: Brian Holmes Attachments: hibernate3-v313-support_schema_catalog_names.patch HSQLDB does not support the use of three part names, that is Tables with schema and catalog parts. This patch adds two functions to Dialect: supportsSchemaNames() and supportsCatalogNames(). Table.getQualifiedName() checks these values to decide whether to use or ignore the schema and catalog parts. By default these are enabled in Dialect. This patch only disables their use in HSQLDialect. This change is necessary for people who normally use Schema and Catalog names for access their primary database, but also use HSQLDB for Unit Testing. Without it, HSQLDB is unusable for Unit Testing because it fails on use of any catalog or schema names. -- 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

13 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3644) Add support for "WITH UR" isolation clause on DB2

by Ricardo Fernandes (JIRA)

Add support for "WITH UR" isolation clause on DB2 ------------------------------------------------- Key: HHH-3644 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3644 Project: Hibernate Core Issue Type: Sub-task Components: core Affects Versions: 3.3.1 Environment: HIbernate 3.3.1 / DB2 9.x Reporter: Ricardo Fernandes The question is basically the same as Steve's, i.e. to force DB2 to use as few locks as possible on heavy load scenarios. Although some might consider the use of the WITH UR clause a bad approach (since it allows dirty reads), the fact is that there are some cases where this is in fact acceptable, such as computing the total amount of rows of a query (for information purposes) or producing a high-level listing of items with very little detailed info. The bottom line is: if I need to trade performance for extremely accurate data, I surely want to be able to decide when this should happen. I've already performed the changes that makes it possible to use both the FOR READ ONLY and the WITH UR clauses and I will be submitting a patch shortly so you can have a look at it. The strategy I've used was basically the following: 1. Added two new methods on the Dialect class: String getDatabaseReadOnlyString(String sql) - for adding the READ ONLY clause String getDirtyReadsString(String sql) - for adding the WITH UR clause 2. Changed the Query interface in order to allow the user to say whether he/she wants the query to allow dirty reads: Query setAllowDirtyReads(boolean allowDirtyReads); 3. Added a default implementation on the AbstractQueryImpl which initializes the flag a false 4. Added a similar attribute on the QueryParameters class 5. Changed the prepareQueryStatement() method of the Loader class (just after the useLimit part in order: a) Ask the dialect for the getDatabaseReadOnlyString() is there are no LockModes set (as did Steve) b) Ask the dialect for the getDirtyReadsString() is the queyParameters allows dirty reads. All the tests were well succeeded. Hope you find these changes, at least, worth looking at. Best Regards, Ricardo -- 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

13 years, 5 months

7
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3458) Register postgres random() function as "rand" in PostgresSQLDialect

by Stephen Cresswell (JIRA)

Register postgres random() function as "rand" in PostgresSQLDialect ------------------------------------------------------------------- Key: HHH-3458 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3458 Project: Hibernate3 Issue Type: Improvement Components: build Affects Versions: 3.2.5 Environment: Postgres 8.3 Reporter: Stephen Cresswell Priority: Trivial I have an HQL query which uses "order by rand()". This works fine in our local integration tests (which are run against hsqldb), but fails against our build integration tests which runs postgres. The reason the query fails is because postgres function for "rand" is called "random". We can workaround this by dynamically detecting the db driver and generating db specific queries, but it strikes me that the cleanest solution for this is to simply re-register postgres' random function as "rand" in the PostgresSQLDialect, i.e. registerFunction( "random", new NoArgSQLFunction("random", Hibernate.DOUBLE) ); registerFunction( "rand", new NoArgSQLFunction("random", Hibernate.DOUBLE) ); -- 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

13 years, 5 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2805) The class Order does not contain getters

by Aviad Lichtenstadt (JIRA)

The class Order does not contain getters ---------------------------------------- Key: HHH-2805 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2805 Project: Hibernate3 Issue Type: Improvement Components: query-criteria Affects Versions: 3.2.5 Reporter: Aviad Lichtenstadt Priority: Trivial Attachments: HibernateOrder.txt The class Order does not contain getters. This is way it is impossible to know if the ignoreCase field was set. This issue becomes more important using Hibernate Shards project. Using Shards the ordering is done using java and there is no way today to know is this property is set. i am applying a patch that adds this getter -- 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

13 years, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2721) PostgreSQLDialect: function md5() always returns a string value

by Dirk Leser (JIRA)

PostgreSQLDialect: function md5() always returns a string value --------------------------------------------------------------- Key: HHH-2721 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2721 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4.sp1 Reporter: Dirk Leser Priority: Minor The md5() function always returns a string type and not the type given as parameter. Therefore the line registerFunction( "md5", new StandardSQLFunction("md5") ); has to be changed to registerFunction( "md5", new StandardSQLFunction("md5", Hibernate.STRING) ); in class org.hibernate.dialect.PostgreSQLDialect -- 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

13 years, 5 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2448) Generate identical column aliases among cluster

by Loïc LEFEVRE (JIRA)

Generate identical column aliases among cluster ----------------------------------------------- Key: HHH-2448 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2448 Project: Hibernate3 Type: Improvement Components: query-sql Versions: 3.2.2 Environment: Hibernate version: 3.2.2, 2.1.8 Database: Oracle 9.2.0.8 Reporter: Loïc LEFEVRE Attachments: report_1.txt, report_2.txt Among our weblogic cluster (12 instances), we can see that a query can have different column aliases. Although all seems correct, when regarding database reports like StatsPack or Spotlight we can see that because of these different aliases, the reports are wrong. Indeed, a resource consuming query can see its associated report properties (cpu usage, buffer gets, number of executions...) divided by the number of weblogic instances of our cluster (i.e. divided by 12) thus preventing us to pinpoint the queries to look at. On a 3 instances cluster, we can see this report: REPORT#1: one statement with a poor number of buffer gets/execution is reported splitted in 3, see the alias generated for column DTO.CREATION_DATE for example On a 4 instances cluster, we can see this report: REPORT#2: one statement responsible of the latch free/cache buffers chains wait events splitted in 4, note the column alias generated fordeffcashcy0_.BEST_EXPECTED_CY More than confusing the DBAs about the same query with n different "faces", our reports don't show us all the queries to look at: indeed, in our "Top 50 queries", a lot of them are duplicates! Also the memory required in the SGA to store the queries, the execution plan and so on is increased... Finally, although the column aliases can have up to 30 characters under Oracle, the limit is set to 10, why? -- 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

13 years, 5 months

15
43
0 / 0

[Hibernate-JIRA] Created: (ANN-787) @UniqueConstraint annotation not creating unique indexes

by Avinash THM (JIRA)

@UniqueConstraint annotation not creating unique indexes -------------------------------------------------------- Key: ANN-787 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-787 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: hibernate-core 3.3.1GA, hibernate-annotations 3.4.0GA, DB2 version 9.1 Reporter: Avinash THM Priority: Minor Unique indexes are not being created when using @UniqueConstraint annotation. The tables are created properly with primary keys and foreign keys, but the unique indexes are not created. I have posted the issue in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=991505&highlight=) but didnt get any reply. I have also seen a couple of posts for the same problem. can anybody help me out with this issue? -- 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

13 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3465) HiRDB Support

by Tomoto Shimizu Washio (JIRA)

HiRDB Support ------------- Key: HHH-3465 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3465 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.5 Environment: 3.2.5 + HiRDB V8 + Type4 JDBC Driver Reporter: Tomoto Shimizu Washio Attachments: hirdbdialect.patch I would like to contribute with a dialect for HiRDB, Hitachi's RDBMS. (For more information, please see http://www.hitachi.co.jp/Prod/comp/soft1/global/prod/hirdb/) I added 4 classes and slightly modified 2 existing classes as shown below. Please look at the documentation at the top of the patch for explanations. org.hibernate.dialect.HiRDBDialect (added) org.hibernate.dialect.UserFuncDeclParser (added) org.hibernate.dialect.DialectFactory (modified) org.hibernate.dialect.function.AnsiTrimEmulationFunction (modified) org.hibernate.dialect.function.AnsiTrimEmulationFunctionWithTrimstrs (added) org.hibernate.dialect.function.TypeQualifiedSQLFunction (added) You may think this code is relatively large as a dialect. It is because I also implemented user-defined function support. As HiRDB requires '?' parameters to be qualified by 'as <type>' in user-defined function invocations, I made a parser for the type declarations that the user specified in the properties file, and a renderer for the type qualifier. See javadoc comments of HiRDBDialect and UserFuncDeclParser for more details. This patch is created on Hibernate 3.2.5.ga and tested on HiRDB V8 with Type4 JDBC Driver. The example configuration for HiRDB is shown below: hibernate.dialect org.hibernate.dialect.HiRDBDialect hibernate.connection.driver_class JP.co.Hitachi.soft.HiRDB.JDBC.HiRDBDriver hibernate.connection.url jdbc:hitachi:hirdb://DBID=@HIRDBENVGRP=C:/hirdb.ini hibernate.connection.username hitachi hibernate.connection.password hitachi -- 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

13 years, 5 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3367) Add support to OpenEdge RDMS (Progress 10) in DialectFactory

by Glaucio Scheibel (JIRA)

Add support to OpenEdge RDMS (Progress 10) in DialectFactory ------------------------------------------------------------ Key: HHH-3367 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3367 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.6 Reporter: Glaucio Scheibel Attachments: DialectFactory.java, DialectFactory.patch This patch adds OpenEdge (formely Progress Database) support to DialectFactory class. -- 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

13 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2654) Ingres dialect patch to support bit_length

by Chris Bredesen (JIRA)

Ingres dialect patch to support bit_length ------------------------------------------ Key: HHH-2654 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2654 Project: Hibernate3 Issue Type: Patch Components: core Reporter: Chris Bredesen Assignee: Steve Ebersole Priority: Minor Attachments: IngresDialect.diff This patch from Daniel fixes the Ingres dialect to support bit_length. -- 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

13 years, 5 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2308) Adjusting the Outer Join Predicate using Criteria Query

by Ben Grant (JIRA)

Adjusting the Outer Join Predicate using Criteria Query ------------------------------------------------------- Key: HHH-2308 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2308 Project: Hibernate3 Type: New Feature Components: query-criteria Versions: 3.2.1 Environment: Linux Using MS SQLServer Reporter: Ben Grant I have two tables Table A ||Col_1||Col_2|| |London| UK | |Liverpool| UK | | New York | USA | Table B ||Col_1||Col_2|| Col_3|| | UK | Europe | 0 | USA | Americas | 1 Using the Criteria class, Restriction Class and FetchMode, Hibernate manages to create a query that looks like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 where TableB3_.Col_3=1 When really i need the query to be like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 AND TableB3_.Col_3=1 currently their isn't any know way for hibernate to adjust or apply filters within the join 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

13 years, 5 months

12
27
0 / 0

[Hibernate-JIRA] Created: (HHH-2844) Limit and 'For Update' do not work on Oracle

by Michael Kopp (JIRA)

Limit and 'For Update' do not work on Oracle -------------------------------------------- Key: HHH-2844 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2844 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.2 Reporter: Michael Kopp Limits on oracle lead too: select * from (select x.y as xy_1 from table x) where rownum <= 5 when doing a for update that leads too select * from (select x.y as xy_1 from table x) where rownum <= 5 for update of x.y The problem is that the x.y is invalid and not found within the temporary view and leads to an oracle error. what would be valid is the name of the view column xy_1, meaning select * from (select x.y as xy_1 from table x) where rownum <= 5 for update of xy_1 Actually this should be valid in all cases when doing a alias for update lock. My Solution thus was to override the following in my own Oracle Dialect public String applyLocksToSql(final String sql, final Map aliasedLockModes, final Map keyColumnNames) { final String s = new ForUpdateFragment(this, aliasedLockModes, keyColumnNames) { @Override public ForUpdateFragment addTableAlias(final String alias) { // search for alias in sql final int i = sql.indexOf(alias); // check if the found string is followed by an ' as ' and thus has a column alias if (i != -1 && sql.length() > (i + alias.length() + 4) && sql.substring(i + alias.length(), i + alias.length() + 4).equals( " as ")) { // use the column alias return super.addTableAlias(sql.substring(i + alias.length() + 4, sql.indexOf(',',i + alias.length() + 4))); } return super.addTableAlias(alias); } }.toFragmentString(); return sql + s; -- 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

13 years, 6 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HBX-939) Composite IDs and many-to-many relationships

by Markus Kramer (JIRA)

Composite IDs and many-to-many relationships -------------------------------------------- Key: HBX-939 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-939 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2beta9 Environment: Hibrnate 3.2.1, Postgresql 8.1.8 Reporter: Markus Kramer Attachments: B.hbm.xml, testdb.sql The detection of many-to-many relationships doesn't work correctly if the primary key of one of the involved tables consists of more than one field. An example: One of two tables (table 'A') of a many-to-many relationship has a primary key consisting of two attributes (id1 and id2). The generated B.hbm.xml for the table 'B' contains this: <set name="as" inverse="true" table="a_b"> <key> <column name="b_id" not-null="true" /> </key> <many-to-many entity-name="test.A"> <column name="a_id1" not-null="true" /> </many-to-many> </set> But there should be another entry for the referenced primary key: <column name="a_id2" not-null="true" /> The SQL code for the used tables and the complete B.hbm.xml are 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

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2058) puhs SessionImplementor.getInterceptor up into Session

by Max Rydahl Andersen (JIRA)

puhs SessionImplementor.getInterceptor up into Session ------------------------------------------------------ Key: HHH-2058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2058 Project: Hibernate3 Type: Improvement Components: core Reporter: Max Rydahl Andersen Being able to get the actual interceptor used for a certain Session is beneficial. any reason why it is not exposed on Session ? -- 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

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3129) Null Role in PersitentCollection during a onCollectionRecreate() in an Interceptor

by Jose CHILLAN (JIRA)

Null Role in PersitentCollection during a onCollectionRecreate() in an Interceptor ---------------------------------------------------------------------------------- Key: HHH-3129 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3129 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Any Reporter: Jose CHILLAN When the "onCollectionRecreate" is invoked on an Interceptor, the getRole() method returns null. After investigation, the problem is located in the class CollectionEntry in one of its constructors and is easily solved using the patch : public CollectionEntry(CollectionPersister persister, PersistentCollection collection) { // new collections that get found + wrapped // during flush shouldn't be ignored ignore = false; collection.clearDirty(); //a newly wrapped collection is NOT dirty (or we get unnecessary version updates) snapshot = persister.isMutable() ? collection.getSnapshot(persister) : null; // -- ADDED LINE HERE -- role = persister.getRole(); collection.setSnapshot(loadedKey, role, snapshot); } Thanks -- 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

13 years, 6 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2847) THIS_"."NAME": invalid identifier when using createCriteria with addOrder

by Ashish Tiwari (JIRA)

THIS_"."NAME": invalid identifier when using createCriteria with addOrder ------------------------------------------------------------------------- Key: HHH-2847 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2847 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.0.5 Environment: Oracle - 10.2.0 Reporter: Ashish Tiwari We are using hibernate 3.0.5 and once a while I see following error getting generated due to incorrect SQL generated by hibernate: Hibernate: select systembean0_.SYSTEMID as SYSTEMID12_0_, systembean0_.Version as Version12_0_, systembean0_.NAME as NAME12_0_, systembean0_.TYPE as TYPE12_0_, systembean0_.DESCRIPTION as DESCRIPT5_12_0_ from SDSYSTEM systembean0_ order by this_.NAME asc - SQL Error: 904, SQLState: 42000 - ORA-00904: "THIS_"."NAME": invalid identifier This normally works but occasionally we run into the issue mentioned above. I do not see alias "this_" in the sql query and I think that causes the error to happen. Issue is caused by alias not used consistently. In normal case the generated SQL looks like following: Hibernate: select this_.SYSTEMID as SYSTEMID7_0_, this_.Version as Version7_0_, this_.NAME as NAME7_0_, this_.TYPE as TYPE7_0_, this_.DESCRIPTION as DESCRIPT5_7_0_ from SDSYSTEM this_ order by this_.NAME asc I am not sure what causes this problem. Has anyone else see similar problem earlier? I appreciate any help with this. Below is other information: Hibernate version: 3.0.5 Mapping documents: <?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> <class name="com.avaya.coreservice.admin.toolkit.common.system.SystemBean" table="SDSYSTEM"> <id name="uniqueId" type="java.lang.String"> <column name="SYSTEMID" length="50" not-null="true"/> <generator class="uuid"/> </id> <version name="version" column="Version" /> <property name="name" type="java.lang.String"> <column name="NAME" length="512" not-null="true"/> </property> <property name="type" type="java.lang.String"> <column name="TYPE" length="50" not-null="false"/> </property> <property name="description" type="java.lang.String"> <column name="DESCRIPTION" length="1024" not-null="false"/> </property> <set name="resourceBeanSet"> <key> <column name="SYSTEMID" length="50" not-null="false"/> </key> <one-to-many class="com.avaya.coreservice.admin.toolkit.common.resource.ResourceBean"/> </set> <set name="siteBeanSet" order-by="name asc"> <key> <column name="SYSTEMID" length="50" not-null="false"/> </key> <one-to-many class="com.avaya.coreservice.admin.toolkit.common.site.SiteBean"/> </set> </class> </hibernate-mapping> Code between sessionFactory.openSession() and session.close(): HibernateUtil.getSession().createCriteria(SystemBean.class) .addOrder(Order.asc("name")).list(); Full stack trace of any exception that occurs: N/A Name and version of the database you are using: Oracle - 10.2.0 The generated SQL (show_sql=true): select systembean0_.SYSTEMID as SYSTEMID12_0_, systembean0_.Version as Version12_0_, systembean0_.NAME as NAME12_0_, systembean0_.TYPE as TYPE12_0_, systembean0_.DESCRIPTION as DESCRIPT5_12_0_ from SDSYSTEM systembean0_ order by this_.NAME asc I appreciate any help with this. Thanks, -- 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

13 years, 6 months

7
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3345) "select new" + "join fetch" = "owner of the fetched association was not present in the select list"

by Anthony Ogier (JIRA)

"select new" + "join fetch" = "owner of the fetched association was not present in the select list" --------------------------------------------------------------------------------------------------- Key: HHH-3345 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3345 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Reporter: Anthony Ogier I want to create a List<B>, each B containing an entity with "A" type, and I also want for each A to force fetching of its "C" property. public class B { private A a; public B(A a) { this.a = a; } } @Entity public class A { @ManyToOne @JoinColumn private C c; // +get/setter ... } @Entity public class C { @Column private String d; // +get/setter ... // +@OneToMany } Here is the HQL : select new B(a) from A a left join fetch a.c I have that message : org.hibernate.QueryException: query specified join fetching, but the owner of the fetched association was not present in the select list When invoking only "from A a left join fetch a.c", all is good and I have ma List<A> with its "C" properties fetched. I think there is a little bug here ... or did I forget something ? -- 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

13 years, 7 months

4
3
0 / 0

[Hibernate-JIRA] Created: (ANN-537) Support @Comment or column attribute on @Table and @Column

by Max Rydahl Andersen (JIRA)

Support @Comment or column attribute on @Table and @Column ---------------------------------------------------------- Key: ANN-537 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-537 Project: Hibernate Annotations Type: Improvement Components: binder Versions: 3.2.1 Reporter: Max Rydahl Andersen with hbm2ddl and hbm2doc its a shame that Annotation does not support setting a comment on table and columns. -- 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

13 years, 7 months

9
22
0 / 0

[Hibernate-JIRA] Created: (ANN-783) DOCS: says, monkey, should say tiger: section 2.2.5.3.2.4. Defaults

by Karl Palsson (JIRA)

DOCS: says, monkey, should say tiger: section 2.2.5.3.2.4. Defaults ------------------------------------------------------------------- Key: ANN-783 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-783 Project: Hibernate Annotations Issue Type: Improvement Components: documentation Affects Versions: 3.4.0.GA Environment: http://www.hibernate.org/hib_docs/annotations/reference/en/html_single/ or http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.ht... Reporter: Karl Palsson Priority: Trivial Text says: Trainer describes a unidirectional relationship with Tiger using the join table Trainer_Tiger, with a foreign key trainer_id to Trainer (table name, _, trainer id) and a foreign key trainedTigers_id to Monkey (property name, _, Tiger primary column). Last reference to Monkey should say Tiger. Monkeys were used in the previous section -- 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

13 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2796) Generated version are incremented by Hibernate

by Heba Tawfik (JIRA)

Generated version are incremented by Hibernate ---------------------------------------------- Key: HHH-2796 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2796 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.1 Environment: 3.2.1, Oracle 10g Reporter: Heba Tawfik Creating a new entity which it's version is set to generated="always" & saving it, then in the same session adding an object to any of its on-to-many relationships is throwing a StaleObjectStateException. To regenerate the problem, consider the following code 1- departement.hbm.xml : ---------------------------------------- <hibernate-mapping package="com.myproject.domain"> <class name="Departement" table="Departement"> <id name="id"> <column name="dept_id" /> </id> <version column="version" generated="always" name="version" type="integer" unsaved-value="null" /> <property name="name" column="name" /> <bag name="employees" inverse="true" cascade="all" lazy="true"> <key column="dept_id"></key> <one-to-many class="Employee" /> </bag> </class> </hibernate-mapping> 2- employee.hbm.xml : -------------------------------------- <hibernate-mapping package="com.myproject.domain"> <class name="Employee" table="Employee"> <id name="id"> <column name="employee_id" /> </id> <property name="firstName" column="first_name" /> <property name="lastName" column="last_name" /> <property name="age" column="age" /> <property name="salary" column="salary" /> <many-to-one cascade="none" class="com.myproject.domain.Departement" column="dept_id" embed-xml="true" insert="false" name="department" not-null="false" unique="false" update="false" not-found="ignore"> </many-to-one> </class> </hibernate-mapping> 3- Departement.Java --------------------------- package com.myproject.domain; import java.util.ArrayList; import java.util.List; public class Departement extends BaseDepartement{ int id; String name; List employees; Integer version; public int getId() { return id; } public void setId(int id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } public Integer getVersion() { return version; } public void setVersion(Integer version) { this.version = version; } public List getEmployees() { return employees; } public void setEmployees(List employees) { this.employees = employees; } public void addToEmployeeList(Employee emp) { if(employees==null) { setEmployees(new ArrayList()); } employees.add(emp); } } 4- Employee.Java : --------------------------- package com.myproject.domain; public class Employee { int id; String firstName; String lastName; int age; int salary; BaseDepartement department; public BaseDepartement getDepartment() { return department; } public void setDepartment(BaseDepartement department) { this.department = department; } public int getAge() { return age; } public void setAge(int age) { this.age = age; } public String getFirstName() { return firstName; } public void setFirstName(String firstName) { this.firstName = firstName; } public int getId() { return id; } public void setId(int id) { this.id = id; } public String getLastName() { return lastName; } public void setLastName(String lastName) { this.lastName = lastName; } public int getSalary() { return salary; } public void setSalary(int salary) { this.salary = salary; } } 4- Code To Test : ------------------------ public static void main(String args[]) throws Exception { SessionFactory factory = new Configuration().configure("com/myproject/config/hibernate.cfg.xml").buildSessionFactory(); Session session = factory.openSession(); Transaction transaction = session.beginTransaction(); Departement aDept =new Departement(); aDept.setId(10); aDept.setName("Test"); session.save(aDept); transaction.commit(); transaction = session.beginTransaction(); Employee emp=new Employee(); emp.setId(10); emp.setFirstName("test"); emp.setLastName("test"); emp.setSalary(10); emp.setAge(10); emp.setDepartment(aDept); aDept.addToEmployeeList(emp); session.saveOrUpdate(aDept); transaction.commit(); session.close(); } On the database, the default value for version cloumn is set to "1" and a trigger is defined as follow on the Departement table: create or replace TRIGGER TRIGGER1 BEFORE UPDATE ON DEPARTEMENT FOR EACH ROW BEGIN :new.version:= :old.version + 1; END; Upon executing the above code, the following is the hibernate logging : automatically flushing session /* insert com.eds.myproject.domain.Departement */ insert into Departement (name, dept_id) values (?, ?) binding 'Test' to parameter: 1 binding '10' to parameter: 2 /* get generated state com.eds.myproject.domain.Departement */ select departemen_.version as version1_ from Departement departemen_ where departemen_.dept_id=? binding '10' to parameter: 1 returning '1' as column: version1_ before transaction completion after transaction completion automatically flushing session /* get current state com.eds.myproject.domain.Employee */ select employee_.employee_id, employee_.first_name as first2_0_, employee_.last_name as last3_0_, employee_.age as age0_, employee_.salary as salary0_ from Employee employee_ where employee_.employee_id=? binding '10' to parameter: 1 /* insert com.eds.myproject.domain.Employee */ insert into Employee (first_name, last_name, age, salary, employee_id) values (?, ?, ?, ?, ?) binding 'test' to parameter: 1 binding 'test' to parameter: 2 binding '10' to parameter: 3 binding '10' to parameter: 4 binding '10' to parameter: 5 /* update com.eds.myproject.domain.Departement */ update Departement set name=? where dept_id=? and version=? binding 'Test' to parameter: 1 binding '10' to parameter: 2 binding '2' to parameter: 3 Could not synchronize database state with session org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [com.eds.myproject.domain.Departement#10] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1714) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2357) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2257) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2557) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at com.eds.myproject.test.Test.main(Test.java:43) org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [com.eds.myproject.domain.Departement#10] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1714) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2357) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2257) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2557) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at com.eds.myproject.test.Test.main(Test.java:43) -- 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

13 years, 7 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2776) Restrictons.in(..) generates invalid SQL if list of values is empty

by Adrian Smith (JIRA)

Restrictons.in(..) generates invalid SQL if list of values is empty ------------------------------------------------------------------- Key: HHH-2776 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2776 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.2 Environment: Hibernate 3.2.2.ga, MySQL 4.1.18, Windows XP Reporter: Adrian Smith I have classes called A and B. There is a 1:n relationship from A to B. Class B has the following in its mapping file: <many-to-one name="a" class="A" column="fk_a_id" not-null="true" /> If I write the following code: List<B> foo() { List<A> aList = .... Session session = .... Criteria query = session.createCriteria(B.class); query.add(Restrictions.in("a", aList)); return query.list(); } Then all works fine and the results I want are returned. However, if aList is empty (i.e. aList.size()==0) then the query.list function generates and executes invalid SQL for MySQL. java.sql.SQLException: Syntax error or access violation message from server: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1" I imagine that it is generating SQL like IN () which isn't valid. I realize it's a bit ridiculous to want to find the rows where a field is IN the empty list. Nothing will ever be returned. However, in my opinion it should still be allowed, and return no rows, just as saying "WHERE 1=2" is allowed, just doesn't return any rows. -- 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

13 years, 7 months

6
12
0 / 0

[Hibernate-JIRA] Created: (HHH-2831) Native SQL queries with addJoin or <return-join/> return object arrays instead of single Entities

by Jeremy Grodberg (JIRA)

Native SQL queries with addJoin or <return-join/> return object arrays instead of single Entities ------------------------------------------------------------------------------------------------- Key: HHH-2831 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2831 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.5, 3.2.4 Environment: Hibernate 3.2.4.ga and 3.2.5.ga with hsqldb on Win XP Reporter: Jeremy Grodberg Attachments: NativeSQLQueriesTest.patch Although the documentation is not crystal clear, I read it to say that using addJoin should eagerly fetch an associated object but should NOT return it as a separate value. In section 16.1.3. "Handling associations and collections" of the online documentation it says: "It is possible to eagerly join in the Dog to avoid the possible extra roundtrip for initializing the proxy. This is done via the addJoin() method, which allows you to join in an association or collection." This comes BEFORE the section on returning multiple entities, so I say the documentation at least implies it will only return a single entity at the top level. Also, if the intention is to return multiple entities, addEntity() works fine for that, so what then would be the difference of addJoin()? If I'm wrong about what addJoin() should do, please clarify that in the documentation and also clarify how, if it is possible, one could eagerly fetch the association without changing the return type of the quer y. I have reproduced this problem in the Hibernate JUnit tests in 3.2.4.ga and 3.2.5.ga, specifically NativeSQLQueriesTest.testSQLQueryInterface(). I'm attaching a patch to the Hibernate junit test org.hibernate.test.sql.hand.query.NativeSQLQueriesTest.java released in 3.2.5.ga that adds a test to ensure that a query with addJoin only returns a (list of) entities, not a list of Object arrays containing entities. Currently, the assertion fails because instead of returning a list of Organizations we get a list of Object[3] = { Organization, Employment, Person }, which is exactly what we get when the addJoin()s are replaced with appropriate addEntity() calls. -- 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

13 years, 7 months

14
15
0 / 0

[Hibernate-JIRA] Created: (HHH-3606) Can't use distinct in Oracle with BLOB/CLOB column

by Julien HENRY (JIRA)

Can't use distinct in Oracle with BLOB/CLOB column -------------------------------------------------- Key: HHH-3606 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3606 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Oracle 9i Reporter: Julien HENRY Problem: Oracle doesn't support distinct when a row is BLOB/CLOB. The resulting error is: ORA-00932: inconsistent datatypes: expected - got CLOB I got this error when trying to filter root entity (see FAQ: http://www.hibernate.org/117.html#A12). It is not really an Hibernate bug, much likely an Oracle limitation. But perhaps an entry may be added in the FAQ, or perhaps some workaround may be found to not use SQL distinct keyword when a BLOB/CLOB is involved in the query. Some related links: http://drupal.org/node/48435 (FR) http://www.developpez.net/forums/d553106/java/general-java/persistance/hi... http://www.dbasupport.com/forums/showthread.php?t=46785 (possible rewriting of the query) -- 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

13 years, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2969) DB2Dialect Clob SchemaExport uses default length even if no length set

by Philippe Mouawad (JIRA)

DB2Dialect Clob SchemaExport uses default length even if no length set ---------------------------------------------------------------------- Key: HHH-2969 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2969 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, DB2 8, DB2 9 Reporter: Philippe Mouawad Attachments: db2-clob-schemaExport-patch.txt I have this property in my mapping: <property name="argumentsValues" column="cte_arguments_values" type="text" not-null="true" /> Notice no length is set. Hibernate schema Export generates: cte_arguments_names clob(255) not null, Same problem occurs for Clob and Blob. This is due to the following lines in org.hibernate.dialect.DB2Dialect: registerColumnType( Types.BLOB, "blob($l)" ); registerColumnType( Types.CLOB, "clob($l)" ); Attached is the patch. There would be another solution to test that Column has no length set. Philippe. www.ubik-ingenierie.com -- 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

13 years, 7 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3298) Hibernate does not correcly apply LockMode.UPGRADE when performing a polymorphic select to a leaf-class via a mapped superclass on Oracle

by Mike Everett (JIRA)

Hibernate does not correcly apply LockMode.UPGRADE when performing a polymorphic select to a leaf-class via a mapped superclass on Oracle ----------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3298 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3298 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, Oracle 10gR2 Reporter: Mike Everett Attachments: src.zip Greetings All, I'm experiencing an issue with Hibernate generated SQL when I attempt to retrieve a union-subclass entity via a concrete mapped superclass with LockMode.UPGRADE. Hibernate will generate SQL with a UNION ALL of the sub-classes and then apply FOR UPDATE to the query which is not allowed with Oracle. This leads to the following error: java.sql.SQLException: ORA-02014: cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc. It seems that "etc." part includes UNION and UNION ALL. Example with three classes: Entity (abstract) <--extends--- ConcreteInheritorOne (concrete) <--extends-- ConcreteInheritorTwo (concrete) assume: inheritorTwoId == the id of an item of class ConcreteInheritorTwo session == a Hibernate Session // These lookups will cause the error Entity e = (Entity) session.get(Entity.class, inheritorTwoId, LockMode.UPGRADE); Entity e = (Entity) session.get(ConcreteInheritorOne.class, inheritorTwoId, LockMode.UPGRADE); // This will not cause the error Entity e = (Entity) session.get(ConcreteInheritorTwo.class, inheritorTwoId, LockMode.UPGRADE); I have attached entity classes and a Test class which illustrate this effect. I spelunked into the code a bit, but an easy fix did not present itself to my hibernate-code-virgin eyes. Thanks for making Hibernate great! --Mje #### Workaround #### If anyone else is experiencing this problem, I've implemented code similar to the method below as a work-around in an abstraction layer: public Object getEntityForUpdate(Class entityClass, String entityId) { Session s = getSession(); ClassMetadata meta = s.getSessionFactory().getClassMetadata(entityClass); Boolean doTwoPhaseLock = false; if(meta instanceof UnionSubclassEntityPersister) { if(((UnionSubclassEntityPersister)meta).getEntityMetamodel().getSubclassEntityNames().size() > 1) doTwoPhaseLock = true; } if(doTwoPhaseLock) { Entity e = (Entity)s.get(entityClass, entityId); System.out.println("Using Two-Phase Lock on: EntityId[" + entityId + "] EntityClass[" + entityClass.getName() + "]"); s.lock(e, LockMode.UPGRADE); return e; } else { System.out.println("Using One-Phase Lock on: EntityId[" + entityId + "] EntityClass[" + entityClass.getName() + "]"); return s.get(entityClass, entityId, LockMode.UPGRADE); } } #### Hibernate Generated SQL Example #### select entity0_.id as id6_0_, entity0_.versionNumber as versionN2_6_0_, entity0_.clazz_ as clazz_0_ from ( select versionNumber, id, 2 as clazz_ from BASE_ConcreteInheritorTwo union all select versionNumber, id, 1 as clazz_ from BASE_ConcreteInheritorOne ) entity0_ where entity0_.id=? for update #### Stack Trace #### 15:18:14,484 ERROR JDBCExceptionReporter:78 - ORA-02014: cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc. 15:18:14,484 INFO DefaultLoadEventListener:111 - Error performing load command org.hibernate.exception.SQLGrammarException: could not load an entity: [org.example.domain.hibernate.Entity#1211505494256] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.loadEntity(Loader.java:1874) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3049) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:399) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:375) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139) at org.hibernate.event.def.DefaultLoadEventListener.lockAndLoad(DefaultLoadEventListener.java:297) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:106) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:869) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:864) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:301) at $Proxy0.get(Unknown Source) at org.example.test.Test.doTest2(Test.java:68) at org.example.test.Test.main(Test.java:35) Caused by: java.sql.SQLException: ORA-02014: cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc. at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:745) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:810) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:850) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1134) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3339) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3384) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.loadEntity(Loader.java:1860) ... 19 more -- 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

13 years, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3011) merge() optimization for Oracle dialect

by MG (JIRA)

merge() optimization for Oracle dialect --------------------------------------- Key: HHH-3011 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3011 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: MG Priority: Minor merge() optimization for Oracle dialect. Since 9i Oracle has a MERGE statement which is very useful to save round trips to database in merge() call which will make dramatic improvement for performance of loading large row sets. MERGE command processes the conditional INSERT-or-UPDATE within a single statement. So instead of doing 'select' first to detect whether entity is in database or not (This is one round trip to DB) and then issuing 'update' or 'insert' all of it could be done in one statement with no extra round trips using oracle SQL MERGE statement. http://www.oracle.com/technology/products/oracle9i/daily/Aug24.html -- 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

13 years, 7 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3317) Entities saved within onPreUpdate() never inserted into db when id generator is sequenze (f.e. oracle)

by Martin Backhaus (JIRA)

Entities saved within onPreUpdate() never inserted into db when id generator is sequenze (f.e. oracle) ------------------------------------------------------------------------------------------------------ Key: HHH-3317 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3317 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: hibernate3.2.6.ga.jar, Oracle 10 Reporter: Martin Backhaus Priority: Minor If you save (insert) a entity within the event preUpdate and the id is a oracle-sequenze, hibernate put the entity to insert in the session-ActionQueue, BUT NEVER INSERTS it. If you use mysql/hsql... where the id is differently generated, the insert happens immediately and no put to the ActionQueue occures. As workaround you can queue the object (to insert) yourself and call save() within the postUpdate-Event. I use this events for historizing some stuff. Inserts within onDelete() works fine. the ids are annotated as shown here: @Id @GeneratedValue(strategy = GenerationType.AUTO) protected Long id = null; -- 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

13 years, 7 months

4
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2657) Bulk select using primary key or natural id

by charbel (JIRA)

Bulk select using primary key or natural id ------------------------------------------- Key: HHH-2657 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2657 Project: Hibernate3 Issue Type: Improvement Reporter: charbel I think that the following methods are really useful once we use hibernate with huge datas in the database: Object[] get(Class,Object[] id): ---------------------------------------- return objects giving their primary key. First check in cache if it exists, if not either use a select in () either create a temporary table if too many ids. Object[] getUsingNaturalId(Class,Object[] id): ---------------------------------------- return objects giving their natural id. the same thing than before. Be careful on the fact that the primary key and the naturalid can be composite objects. -- 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

13 years, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2331) bulk deletes on ID must not use HT_ tables

by Amir Pashazadeh (JIRA)

bulk deletes on ID must not use HT_ tables ------------------------------------------ Key: HHH-2331 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2331 Project: Hibernate3 Type: Improvement Components: core Reporter: Amir Pashazadeh when using bulk deletes hibernate inserts ids of rows which must be deleted in a temporary table (with HT_ prefix); I believe that's just for knowing primary keys of objects which must be deleted and updating caches. so if that is the reason there is no need to do so when deleting on primary key property, (for example "delete from MyEntity where 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

13 years, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-654) Generated SQL includes a column named "null" when referencing a map entry by key and using @LazyCollection(LazyCollectionOption.EXTRA)

by Paul Roe (JIRA)

Generated SQL includes a column named "null" when referencing a map entry by key and using @LazyCollection(LazyCollectionOption.EXTRA) -------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-654 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-654 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.0.ga Environment: Oracle 10g, hibernate 3.2 Reporter: Paul Roe We have an Product entity with a map of RegionProduct by Region. @MapKey(name="region") @OneToMany(mappedBy="product", targetEntity= RegionProductImpl.class, fetch = FetchType.LAZY) @LazyCollection(LazyCollectionOption.EXTRA) private Map<Region, RegionProduct> regionProducts = new HashMap<Region, RegionProduct>(); When accessing an element of the map by key, the SQL that is generated includes a "null" column in the WHERE condition. where regionprod0_.PROD_ID=? and regionprod0_.null=? resulting in the stack trace org.hibernate.exception.SQLGrammarException: could not collection element by index at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.loadEntity(Loader.java:1841) at org.hibernate.loader.entity.CollectionElementLoader.loadElement(CollectionElementLoader.java:72) at org.hibernate.persister.collection.OneToManyPersister.getElementByIndex(OneToManyPersister.java:360) at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:158) at org.hibernate.collection.PersistentMap.get(PersistentMap.java:146) Iterating over the collection works successfully, but populates the entire collection, which is what Extra-Lazy is meant to avoid. -- 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

13 years, 8 months

6
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3280) Remove OracleDialect and Oracle9Dialect

by Diego Plentz (JIRA)

Remove OracleDialect and Oracle9Dialect --------------------------------------- Key: HHH-3280 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3280 Project: Hibernate3 Issue Type: Deprecation Components: metamodel Reporter: Diego Plentz Fix For: 4.x Since they already really old ones. -- 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

13 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2891) Query cache fails on many-to-many select

by Oleg Efimov (JIRA)

Query cache fails on many-to-many select ---------------------------------------- Key: HHH-2891 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2891 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Reporter: Oleg Efimov I have two entities, User and Group, with many-to-many relation: -------------------------------------------------------------------------------------------------- User.hbm.xml <?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 package="test.hibernate"> <class name="User" table="`USER`"> <id name="id" type="long" unsaved-value="null"> <column name="USER_ID" not-null="true"/> <generator class="native"/> </id> <property name="login"> <column name="LOGIN" not-null="true" length="255"/> </property> <bag name="groups" table="USER_GROUP" lazy="false" cascade="none"> <key column="USER_ID"/> <many-to-many class="Group" column="GROUP_ID"/> </bag> </class> </hibernate-mapping> -------------------------------------------------------------------------------------------------- Group.hbm.xml <?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 package="test.hibernate"> <class name="Group" table="`GROUP`"> <id name="id" type="long" unsaved-value="null"> <column name="GROUP_ID" not-null="true"/> <generator class="native"/> </id> <property name="name"> <column name="GROUPNAME" not-null="true" length="100"/> </property> <bag name="users" table="USER_GROUP" lazy="true" inverse="true" cascade="all-delete-orphan"> <key column="GROUP_ID"/> <many-to-many class="User" column="USER_ID"/> </bag> </class> <query name="Group.select.by.login" cacheable="true"><![CDATA[ select user.groups from User user where user.login=? ]]> </query> </hibernate-mapping> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- test.hibernate.User and test.hibernate.Group classes are just simple beans. In Group.hbm.xml there is a query called "Group.select.by.login", it's intended to be cached. So I add corresponding properties to Hibernate configuraition: -------------------------------------------------------------------------------------------------- properties.put("hibernate.cache.provider_class", "org.hibernate.cache.EhCacheProvider"); properties.put("hibernate.cache.use_query_cache", "true"); ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Configuration has no extra parameters. Then I'm trying to execute the query two times: -------------------------------------------------------------------------------------------------- test fragment SessionFactory sessionFactory = configuration.buildSessionFactory(); Session session = null; try { session = sessionFactory.openSession(); Query query = session.getNamedQuery("Group.select.by.login"); List<Group> groups; groups = query.setParameter(0, "admin").list(); // +++++++++++++++This list() returns list of two Group objects, ok +++++++++++++++ System.out.println("-----------------------------------------------------------------------------------"); for (Group group : groups) { System.out.println(group.getName()); } System.out.println("-----------------------------------------------------------------------------------"); groups = query.setParameter(0, "admin").list(); // +++++++++++++++This list() returns list of two nulls +++++++++++++++ System.out.println("-----------------------------------------------------------------------------------"); for (Group group : groups) { System.out.println(group.getName()); } System.out.println("-----------------------------------------------------------------------------------"); } finally { if (session != null) { session.close(); } sessionFactory.close(); } ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The first query returns list of, in my case, two groups. The second query returns list of two nulls instead of the same list. I've investigated the problem, and found the following: Query return value is "user.groups", and during query analysis (org.hibernate.hql.ast.QueryTranslatorImpl:160) query return type is defined as "org.hibernate.type.BagType(test.hibernate.User.groups)". This seems to be the problem, as during query put operation org.hibernate.CollectionType.disassemble is called (org.hibernate.cache.StandardQueryCache:80), which simply returns null as owner is null. If this query is not a misuse, then I think, something is to be done at the time of analysis, so that return type be somewhat different. Thanks. -- 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

13 years, 8 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2049) LEFT OUTER JOIN subcriteria filters children

by Mattias Jiderhamn (JIRA)

LEFT OUTER JOIN subcriteria filters children -------------------------------------------- Key: HHH-2049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2049 Project: Hibernate3 Type: Bug Components: query-criteria Versions: 3.1.3, 3.2.0.cr4 Environment: Hibernate 3.1.3/3.2.0rc4, hsqldb 1.8 Reporter: Mattias Jiderhamn Attachments: SubCriteriaTestCase.zip When using the Criteria API with LEFT OUTER JOIN to add criterias to the children, i.e. criteria.createCriteria("children", JoinFragment.LEFT_OUTER_JOIN) the child collections will only contain those children matching the criteria. (Even when *not* using any Filters). The attached testcase (also found here: http://forum.hibernate.org/viewtopic.php?p=2320786) will explain it in more detail. -- 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

13 years, 8 months

13
52
0 / 0

[Hibernate-JIRA] Created: (HHH-3562) Support @OrderBy and @Sort annotations

by Adam Warski (JIRA)

Support @OrderBy and @Sort annotations -------------------------------------- Key: HHH-3562 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3562 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski -- 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

13 years, 8 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3628) Hilo optimizer problem in case of multiple threads accessing the sequence table

by Montagnon Cyril (JIRA)

Hilo optimizer problem in case of multiple threads accessing the sequence table ------------------------------------------------------------------------------- Key: HHH-3628 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3628 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.6 Environment: Sybase Reporter: Montagnon Cyril If 2 (or more) threads access the table storing the ids, this optimizer won't work and will try to insert entities with twice the same idea. The problem is the way the HiLoOptimizer class generates the id : public synchronized Serializable generate(AccessCallback callback) { if ( lastSourceValue < 0 ) { lastSourceValue = callback.getNextValue(); while ( lastSourceValue <= 0 ) { lastSourceValue = callback.getNextValue(); } hiValue = ( lastSourceValue * incrementSize ) + 1; value = hiValue - incrementSize; } else if ( value >= hiValue ) { lastSourceValue = callback.getNextValue(); hiValue = ( lastSourceValue * incrementSize ) + 1; } return make( value++ ); } In the 'else if' part, the 'value' variable isn't reaffected, which means the current thread will try to insert entities with an id that has already been used by another thread. The value should be reset with hiValue - incrementSize. -- 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

13 years, 8 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2223) BatchFetchQueue.getXXXBatch() cache check impeding batch fetching

by Joel Caplin (JIRA)

BatchFetchQueue.getXXXBatch() cache check impeding batch fetching ----------------------------------------------------------------- Key: HHH-2223 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2223 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: 3.2.0GA, Mac OS X/Solaris 10, Sybase 12.5/HSQLDB Reporter: Joel Caplin Priority: Minor Attachments: testcase.tar I have attached a test case which demonstrates the issue at hand by implementing a cheap data model: Pub >---|- Manager -|--< Employee Pub and Employee are uncached; Manager is cached (tried under both Eh and the non-prod HashMap implementation). All associations are lazy. The test case has a default batch size of 10 and uses hsqldb to demonstrate the problem - which was diagnosed against Sybase. When BatchFetchQueue.getXXXBatch() is invoked, it does not load any objects it finds in the second level cache - it merely acknowledges their presence by logging to INFO (isCached()). This in turn means that any child associations in that cached object will not have a proxy created for them. Suppose we want to find all the employees of the pubs in our database. We choose to do this by loading all the Pubs ("FROM Pub") and calling thePub.getManager().getEmployees() iteratively. When the managers are in the second level cache, Hibernate issues 11 select statements: one to load the pubs and one for each distinct manager. When the Managers are not in the cache, Hibernate issues 3 select statements: one to load the pubs, one to load the managers and one to load the employees. A solution might be to load the object from the cache instead of just ignoring it? -- 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

13 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3552) Eagerly load collections when indicated so in the annotation defining the relation

by Adam Warski (JIRA)

Eagerly load collections when indicated so in the annotation defining the relation ---------------------------------------------------------------------------------- Key: HHH-3552 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3552 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski -- 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

13 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3032) On Sybase, a subquery is incorrectly generated, causing ''Incorrect syntax near the keyword 'as'.

by Fernando Galdino (JIRA)

On Sybase, a subquery is incorrectly generated, causing ''Incorrect syntax near the keyword 'as'. ------------------------------------------------------------------------------------------------- Key: HHH-3032 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3032 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, JDK 1.6, IDE Eclipse 3.3, running on Windows XP Reporter: Fernando Galdino I am using Spring 2.5 and Hibernate. I created a method to find a list of ProductPositionData based on an existence of its details represented by class DetalhePosicaoProdutoData. So, there is a relationship 1:n between tables ProductPosition and DetalhePosicaoProduto. public List<ProductPositionData> findAllBy(Date date, String viewCode, String status) { DetachedCriteria subquery = DetachedCriteria.forClass(DetalhePosicaoProdutoData.class); subquery.add(Expression.eq("indSituaRegis", status)); subquery.add(Expression.eq("compositeId.datPosic", date)); subquery.setProjection(Projections.distinct(Property.forName("tipDolar"))); DetachedCriteria criteria = DetachedCriteria.forClass(ProductPositionData.class); criteria.add(Expression.eq("indSituaRegis", status)); criteria.add(Subqueries.exists(subquery)); List<ProductPositionData> list = this.hibernateTemplate.findByCriteria(criteria); return list; } It should generate a query on the format SELECT blablabla FROM xyz WHERE exists (SELECT 1 FROM wyz). In really, running this method, I got a similar query. select [ommitted field names] from dtb_trd_resultado.resu.tbl_posicao_produto_trd this_ where this_.ind_situa_regis=? and exists (select distinct this0__.tip_dolar as y0_ from dtb_trd_resultado.resu.tbl_det_posicao_produto_trd this0__ where this0__.ind_situa_regis=? and this0__.dat_posic=?) It causes the following error running under Sybase: Incorrect syntax near the keyword 'as'. ; nested exception is com.sybase.jdbc2.jdbc.SybSQLException: Incorrect syntax near the keyword 'as'. It happens because on the subquery is generated this0__.tip_dolar as y0_ but "as y0_" is not valid in Sybase because using alias is not allowed for Sybase subqueries. I saw similar problems at: http://forum.hibernate.org/viewtopic.php?t=949233 http://opensource.atlassian.com/projects/hibernate/browse/HHH-2905 ----------------------------------- Stacktrace: org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: could not execute query; uncategorized SQLException for SQL [select this_.tip_orige_opera as tip1_4_0_, this_.num_opera as num2_4_0_, this_.ind_ativo_passi as ind3_4_0_, this_.tip_posic_opera as tip4_4_0_, this_.num_book as num5_4_0_, this_.num_regra_produ as num6_4_0_, this_.tip_objet_opera as tip7_4_0_, this_.tip_opera as tip8_4_0_, this_.num_empre as num9_4_0_, this_.num_clien as num10_4_0_, this_.ind_tradi as ind11_4_0_, this_.dat_inici_opera as dat12_4_0_, this_.dat_termi_opera as dat13_4_0_, this_.dat_termi_opera_me as dat14_4_0_, this_.dat_venci_risco as dat15_4_0_, this_.val_parid_moeda as val16_4_0_, this_.pcl_taxa_opera as pcl17_4_0_, this_.pcl_sobre_index as pcl18_4_0_, this_.val_cotac_indic_abert as val19_4_0_, this_.cod_risco_index as cod20_4_0_, this_.num_confi_calcu_produ as num21_4_0_, this_.cod_indic_econo_indic as cod22_4_0_, this_.tip_indic_econo_indic as tip23_4_0_, this_.nat_indic_econo_indic as nat24_4_0_, this_.tip_merca_indic_indic as tip25_4_0_, this_.cod_indic_econo_taxa as cod26_4_0_, this_.tip_indic_econo_taxa as tip27_4_0_, this_.tip_merca_indic_taxa as tip28_4_0_, this_.nat_indic_econo_taxa as nat29_4_0_, this_.ind_situa_regis as ind30_4_0_, this_.dat_situa_regis as dat31_4_0_, this_.cod_user as cod32_4_0_, this_.num_carte as num33_4_0_, this_.dat_liqui_opera as dat34_4_0_, this_.cod_indic_econo_taxa_fwd as cod35_4_0_, this_.tip_indic_econo_taxa_fwd as tip36_4_0_, this_.tip_merca_indic_taxa_fwd as tip37_4_0_, this_.nat_indic_econo_taxa_fwd as nat38_4_0_, this_.dat_limit_varia_indic as dat39_4_0_, this_.tip_metod_preci as tip40_4_0_, this_.tip_estru_sinte as tip41_4_0_, this_.dat_entra_opera as dat42_4_0_ from dtb_trd_resultado.resu.tbl_posicao_produto_trd this_ where this_.ind_situa_regis=? and exists (select distinct this0__.tip_dolar as y0_ from dtb_trd_resultado.resu.tbl_det_posicao_produto_trd this0__ where this0__.ind_situa_regis=? and this0__.dat_posic=?)]; SQL state [ZZZZZ]; error code [156]; Incorrect syntax near the keyword 'as'. ; nested exception is com.sybase.jdbc2.jdbc.SybSQLException: Incorrect syntax near the keyword 'as'. at org.springframework.jdbc.support.SQLStateSQLExceptionTranslator.translate(SQLStateSQLExceptionTranslator.java:121) at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.translate(SQLErrorCodeSQLExceptionTranslator.java:322) at org.springframework.orm.hibernate3.HibernateAccessor.convertJdbcAccessException(HibernateAccessor.java:424) at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:410) at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:378) at org.springframework.orm.hibernate3.HibernateTemplate.findByCriteria(HibernateTemplate.java:981) at org.springframework.orm.hibernate3.HibernateTemplate.findByCriteria(HibernateTemplate.java:974) at com.jpmorgan.br.databroker.control.productposition.ProductPositionControlImpl.findAllByx(ProductPositionControlImpl.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:301) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy5.findAllByx(Unknown Source) at com.jpmorgan.br.databroker.control.productposition.ProductPositionDataProvider.getData(ProductPositionDataProvider.java:32) at com.jpmorgan.br.databroker.service.OptPriceProcessTest.runProcess(OptPriceProcessTest.java:109) at com.jpmorgan.br.databroker.service.OptPriceProcessTest.testProcess(OptPriceProcessTest.java:88) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: com.sybase.jdbc2.jdbc.SybSQLException: Incorrect syntax near the keyword 'as'. at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:3178) at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2481) at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203) at com.sybase.jdbc2.jdbc.SybStatement.queryLoop(SybStatement.java:1611) at com.sybase.jdbc2.jdbc.SybStatement.executeQuery(SybStatement.java:1596) at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeQuery(SybPreparedStatement.java:96) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2220) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:94) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) at org.springframework.orm.hibernate3.HibernateTemplate$35.doInHibernate(HibernateTemplate.java:991) at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:373) ... 35 more -- 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

13 years, 9 months

8
21
0 / 0

[Hibernate-JIRA] Created: (HHH-2280) Not-Null Constraint-Violation with unidirectional one-to-many mapping

by Robert Herschke (JIRA)

Not-Null Constraint-Violation with unidirectional one-to-many mapping --------------------------------------------------------------------- Key: HHH-2280 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2280 Project: Hibernate3 Type: Bug Versions: 3.2.0.cr4 Environment: Hibernate 3.2.0.cr4, Oracle 10XE Reporter: Robert Herschke Priority: Blocker Attachments: one-to-many-test.zip In some cases it is neccessary to have an unidirectional one-to-many mapping, but not using Join-Tables due to a legacy database system. So it must be possible, to have a one-to-many mapping just via a foreign-key-mapping. The Child-Object must not know the Parent-Object in this case. It must also be possible, to pay respect to a NOT-NULL-Constraint at this foreign-key due to restrictions on legacy database systems. Hibernate doesn't support this, but throw a NOT-NULL-Constraint Violation Exception. The documentation says, "this is unusual" - to which I want to dissent. See the attached testcase for details, that is adopted from your "one-to-many" testcase found in the 3.2.0 sources. -- 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

13 years, 9 months

5
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-78) Incorrect fields are ignored by projection: an exception should be raised

by Emmanuel Bernard (JIRA)

Incorrect fields are ignored by projection: an exception should be raised ------------------------------------------------------------------------- Key: HSEARCH-78 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-78 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.0.beta3 Reporter: Emmanuel Bernard Priority: Minor -- 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

13 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-269) Spell check functionality needed

by John Griffin (JIRA)

Spell check functionality needed -------------------------------- Key: HSEARCH-269 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-269 Project: Hibernate Search Issue Type: New Feature Components: engine, mapping Affects Versions: 3.2.0 Reporter: John Griffin Assignee: John Griffin >From Emmanuel: - more than one field and even more than one index should be the source of the dictionary - declaring which field is part of a dictionary should be declarative @AddToDictionary(name="main-dictionary") (with probably an optional field name(s)) - for a given dictionary name, we need to associate an index and probably a field prefix (to share the same index for all dictionaries). This couold be by annotations or in the configuration (not sure) - this index should be kept like any other DirectoryProvider in the HSearch intrastructure (we could then reuse ReaderProvider internally and don't have leaks). - we will probably add a manual dictionary reindex method and the SpellChecker API should be in the SearchFactory. sf.getDictionary("main-dictionary").spellcheck(word, suggestion); sf.getDictionary("main-dictionary").spellcheck(word, suggestion, entity, properties...); //not sure how useful is this one really sf.getDictionary("main-dictionary").reindex(); this needs to be refined. -- 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

13 years, 9 months

5
13
0 / 0

[Hibernate-JIRA] Created: (HHH-2651) Map binary types for sizes > 32K to BLOB for Derby

by Vincent Massol (JIRA)

Map binary types for sizes > 32K to BLOB for Derby -------------------------------------------------- Key: HHH-2651 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2651 Project: Hibernate3 Issue Type: Improvement Components: metamodel Affects Versions: 3.1.2 Reporter: Vincent Massol Right now (at least with 3.1.2, haven't tried with more recent versions) the binary type is mapped to a VARCHAR. However VARCHARs in Derby have a max size of 32K. So for sized larger than 32K a BLOB should be used instead. -- 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

13 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2697) Can't use := for variable assignment within a SQL-Statement

by Benjamin Gniza (JIRA)

Can't use := for variable assignment within a SQL-Statement ----------------------------------------------------------- Key: HHH-2697 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2697 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Environment: MySQL Datasource, Hibernate 3.2.4.sp1 Reporter: Benjamin Gniza Priority: Minor i found a kind of bug in org.hibernate.engine.query.ParameterParser.java: I have an exotic mysql-statement where I want to use mysql variables. VERY SIMPLE example: SET @pos=0; SELECT @pos:=@pos+1 FROM TABLE; Steps to reproduce: Session s = sessionFactory.openSession(); s.createSQLQuery("SET @pos=0").executeUpdate(); SQLQuery qry = s.createSQLQuery("select @pos:=@pos from SomeTable"); List lst = qry.list(); Exception: org.hibernate.QueryException: Space is not allowed after parameter prefix ':' 'SELECT @pos:=@pos+1 FROM TABLE' at org.hibernate.engine.query.ParameterParser.parse(ParameterParser.java:68) ... ... Suggested fix: ParameterParser Lines 62 to 73: if (c == ':' && (indx + 1 >= stringLength || sqlString.charAt(indx + 1) != '=')) { // named parameter int right = StringHelper.firstIndexOfChar( sqlString, ParserHelper.HQL_SEPARATORS, indx + 1 ); int chopLocation = right < 0 ? sqlString.length() : right; String param = sqlString.substring( indx + 1, chopLocation ); if ( StringHelper.isEmpty( param ) ) { throw new QueryException("Space is not allowed after parameter prefix ':' '" + sqlString + "'"); } recognizer.namedParameter( param, indx ); indx = chopLocation - 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

13 years, 9 months

15
22
0 / 0

[Hibernate-JIRA] Created: (HHH-2165) Change logging level in TableMetadata from INFO to DEBUG or TRACE

by Igor A Tarasov (JIRA)

Change logging level in TableMetadata from INFO to DEBUG or TRACE ----------------------------------------------------------------- Key: HHH-2165 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2165 Project: Hibernate3 Type: Improvement Components: metamodel Versions: 3.2.0.ga Reporter: Igor A Tarasov TableMetadata produce too many output to INFO log level. It good thing if it output be at DEBUG level to not hide other impotant information as service start/stop and other. 20.10.06 18:01:58 INFO [main]: SchemaUpdate - updating schema 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.ChageDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, _version, chagedate, created, service, sum, restbalance, comment, customer_id] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, fk8f40c06527214c11, chagedate, primary] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.CustomerDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [phone, firm, group_id, deleted, fio, id, balance, created, updated, address, email, name, comment] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, primary, fk1892e50924b4a799, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.GroupDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, updated, created, name, comment, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, primary, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.HostDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [tarif_id, server_id, ips, mac, deleted, id, created, updated, name, lastactive, comment, disabled, customer_id] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [ips, name, primary, fk812f2053f280a3b1, mac, deleted, fk812f205327214c11, fk812f20537f1e2ff9] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.HostSessionDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, host_id, starttime, chage, speedou, updatetime, speedin, bytesin, stoptime, bytesou, version] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [fk9a9074b995d39b51, id, primary] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.LoginDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, nickname, updated, created, name, comment, password, deleted, customer_id, disabled] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, name, primary, fk77a0599427214c11, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.PPPAccountDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [tarif_id, login_id, id, server_id, updated, created, comment, deleted, disabled, ip] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, fk507abf087f1e2ff9, primary, fk507abf08f280a3b1, fk507abf08820174d9, deleted] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.PPPSessionDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [callerid, starttime, account_id, updatetime, speedou, chage, speedin, stoptime, bytesou, version, ip, id, ident, bytesin] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, fke19b413144f3fa61, starttime, ident, updatetime, primary, stoptime] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.PaymentDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, _version, created, nalichka, sum, paydate, comment, newbalance, customer_id] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, fk7249f0f127214c11, primary, paydate] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.ServerDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [id, updated, created, name, comment, deleted, ip] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, name, primary, deleted, ip] 20.10.06 18:01:58 INFO [main]: TableMetadata - table found: isp.TarifDO 20.10.06 18:01:58 INFO [main]: TableMetadata - columns: [costsizein, resetprepaidsize, prepaidsizerest, moncost, resetprepaidusages, costusage, resetprepaidtime, deleted, prepaidtimemonthly, costtime, prepaidsizemonthly, id, prepaidusagesrest, monthenddate, costsizeou, created, updated, name, prepaidtimerest, prepaidusagesmonthly, comment, customer_id] 20.10.06 18:01:58 INFO [main]: TableMetadata - foreign keys: [] 20.10.06 18:01:58 INFO [main]: TableMetadata - indexes: [id, primary, fk7893f6d27214c11, deleted] 20.10.06 18:01:58 INFO [main]: SchemaUpdate - schema update complete -- 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

13 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-677) Blob is null with Postgresql

by Aaron Luchko (JIRA)

Blob is null with Postgresql ---------------------------- Key: ANN-677 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-677 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.2.1 Environment: hibernate-3.2.1, hibernate-annotations-3.2.1, postgresql-8.2.5-1.fc7, postgresql-jdbc-8.2.504-1jpp.fc7 and postgresql-8.2-506.jdbc4.jar Reporter: Aaron Luchko Attachments: hibPostgresbug.zip I've found that after a sequence of queries, starting new transactions and clearing the session, a Blob will not be successfully from the database and null will be returned by the InputStream instead. Using the debugger I've followed this into the jdbc code and from what I can tell some message is sent to load the blob but the database replies with an empty set of data which naturally causes the InputStream to read null. I've attached a test case (sorry, no makefile or pom.xml, I just ran it using eclipse) which, for me, replicates the bug. Note I've also used hsqldb and mysql and didn't see the bug with them, only postgresql. thanks, Aaron -- 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

13 years, 9 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HBX-978) unique=true attribute of primary key in generated class prevents the schema to be regenerated

by Ali Sadik Kumlali (JIRA)

unique=true attribute of primary key in generated class prevents the schema to be regenerated --------------------------------------------------------------------------------------------- Key: HBX-978 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-978 Project: Hibernate Tools Issue Type: Bug Environment: OS: Windows Vista 6.0,x86 Database: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc. Eclipse Europa: Version: 3.3.0 Build id: I20070621-1340 HibernateTools-3.2.0.beta10 Reporter: Ali Sadik Kumlali Priority: Minor Hi, When I reverse engineer against Oracle, unique=true attribute is added to @Column annotation of primary key column. But, when I generate schema from these generated files, Oracle throws "ORA-02261: such unique or primary key already exists in the table" error. I first ran into this situation while trying Seam and posted the problem to Seam's forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116478. After I got the response, decided to try it without Seam. Then, downloaded the latest HibernateTools & Eclipse Europa and reverse engineered the schema. I saw that generated classes have unique=true attribute which clearly showed that the problem was related with HibernateTools, not with Seam. Here is the DDL of the table against which I made my test: CREATE TABLE PEOPLE ("ID" NUMBER NOT NULL, "SURNAME" VARCHAR2(50 BYTE), "NAME" VARCHAR2(25 BYTE), CONSTRAINT "PEOPLE_PK" PRIMARY KEY ("ID")); Regards, Ali Sadik Kumlali -- 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

13 years, 9 months

8
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3135) SQL Server Dialect maps BIGINT to NUMERIC(19,0)

by Dominik Enkelmann (JIRA)

SQL Server Dialect maps BIGINT to NUMERIC(19,0) ----------------------------------------------- Key: HHH-3135 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3135 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: MS SQL Server Reporter: Dominik Enkelmann Priority: Trivial The SQLServerDialect.java maps the Hibernate BIGINT type to a NUMERIC(19,0) colum. The result is, that all Long fields in persisten classes map to hibernate-bigints which generate numeric(19,0) database column. Longs are typically used for surrogate primary keys and should be implemented as native SQL BIGINTs where possible. SQL Server supports SQL BIGINT since version 2000. There is a similar issue with the SQL BIT type that should be implemented as a native BIT column in SQL Server. A possible solution could be a pre-.SQL Server 2000 dialect and an updated SQL Server dialect. I filed a more detailed description with workaround in the user forum http://forum.hibernate.org/viewtopic.php?p=2377674#2377674 -- 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

13 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2942) Improve support for PostgreSQL

by Diego Pires Plentz (JIRA)

Improve support for PostgreSQL ------------------------------ Key: HHH-2942 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2942 Project: Hibernate3 Issue Type: Improvement Components: metamodel Reporter: Diego Pires Plentz Assignee: Diego Pires Plentz Priority: Minor Improve support for features in PostgreSQL 7.x and 8.x. I will probably create a new one for 8.x series. I asked for help of postgresql hackers. http://archives.postgresql.org/pgsql-hackers/2007-11/threads.php#00462 Docs index: http://www.postgresql.org/docs/ -- 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

13 years, 10 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HBX-935) H2MetaDataDialect for identity detection

by Max Rydahl Andersen (JIRA)

H2MetaDataDialect for identity detection ---------------------------------------- Key: HBX-935 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-935 Project: Hibernate Tools Issue Type: Sub-task Components: reverse-engineer Affects Versions: 3.2beta9 Reporter: Max Rydahl Andersen Fix For: 3.2beta10 -- 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

13 years, 10 months

4
15
0 / 0

[Hibernate-JIRA] Created: (HHH-2770) Action observers for event listeners

by Christian Bauer (JIRA)

Action observers for event listeners ------------------------------------ Key: HHH-2770 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2770 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Christian Bauer Priority: Minor Talked to Steve about a feature he calls "action observers", which would allow the following use case: - Write a FlushEventListener - Observer for what has been deleted, inserted, updated (action queues) This removes some of the pain that comes from missing communication between listeners. For example, you can easily move code you would traditionally write in an Interceptor into a FlushEventListener if you only need inserted/deleted/udpated records. -- 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

13 years, 11 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3452) Statistics for Criteria Queries

by Rohit N (JIRA)

Statistics for Criteria Queries ------------------------------- Key: HHH-3452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3452 Project: Hibernate3 Issue Type: New Feature Components: query-criteria Reporter: Rohit N Priority: Blocker Criteria Queries are not part of the Query Statistics. This gives an incomplete "picture" to the user. Currently, the Statistics is only for HQL queries. -- 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

13 years, 11 months

9
16
0 / 0

[Hibernate-JIRA] Created: (ANN-630) @ManyToMany and @Index

by Peter K. Guldbæk (JIRA)

@ManyToMany and @Index ---------------------- Key: ANN-630 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-630 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Windows Vista java version "1.5.0_11" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode) Reporter: Peter K. Guldbæk I have trouble adding an index to a column of a table which is part of a many-to-many property mapping. The following example causes a NullPointerException when generating the DDL (the exception can be seen at the end of my post): @Entity @Table(name="usr") public class User implements Serializable { @Id @GeneratedValue(strategy=GenerationType.AUTO) public Integer id; @ManyToMany(targetEntity=Target.class, cascade={}) @Index(name="fkey_usr_target", columnNames="usr_id") @JoinTable(name="usr_target", joinColumns=@JoinColumn(name="usr_id"), inverseJoinColumns=@JoinColumn(name="target_id")) public Collection<Target> targets; } @Entity @Table(name="target") public class Target implements Serializable { @Id @GeneratedValue(strategy=GenerationType.AUTO) public Integer id; @Basic public String myValue; } NullPointerException thrown when an @Index annotation is used with a @ManyToMany: java.lang.NullPointerException at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1594) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:733) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:498) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:277) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1115) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:56) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:299) at org.hibernate.tool.ant.Hbm2DDLExporterTask.execute(Hbm2DDLExporterTask.java:45) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:183) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) at org.apache.tools.ant.Project.executeTarget(Project.java:1298) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1181) at org.apache.tools.ant.Main.runBuild(Main.java:698) at org.apache.tools.ant.Main.startAnt(Main.java:199) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) -- 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

13 years, 11 months

8
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2318) Sometimes wrong classloader used for proxy interfaces

by Jan Wiemer (JIRA)

Sometimes wrong classloader used for proxy interfaces ----------------------------------------------------- Key: HHH-2318 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2318 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Jan Wiemer For some of our business classes we used a Mapping declaring the class to be lazy initialized and providing a proxy interface like e.g.: <class name="TestClassImpl" proxy="TestClass" table="testTable" lazy="true"> ... </class> Using classes mapped this way - e.g. as endpoint of a one to one relation - sporadically leads to exceptions like the following: org.hibernate.PropertyAccessException: IllegalArgumentException occurred while calling setter of test.AbstractTestClass2Impl.testField at org.hibernate.property.BasicPropertyAccessor$BasicSetter.set(BasicPropertyAccessor.java:104) at org.hibernate.tuple.entity.AbstractEntityTuplizer.setPropertyValues(AbstractEntityTuplizer.java:337) at org.hibernate.tuple.entity.PojoEntityTuplizer.setPropertyValues(PojoEntityTuplizer.java:200) at org.hibernate.persister.entity.AbstractEntityPersister.setPropertyValues(AbstractEntityPersister.java:3514) at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:129) at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:842) at org.hibernate.loader.Loader.doQuery(Loader.java:717) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.doList(Loader.java:2211) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2095) at org.hibernate.loader.Loader.list(Loader.java:2090) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:388) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:804) Note that the application is residing in a different classloader than hibernate (and CGLIB...). Examining the situation we see that the value passed to the setter was a CGLIB proxy. Internally the proxy stores an array of interfaces the proxy should implement. In our situation this interface contains the HibernateProxy interface and our business interface provided as proxy interface in the mapping. In this interface array we checked the classloader of the interfaces. As expected the HibernateProxy interface is loaded by the system classloader and our interface was loaded by our custom classloader. However examining the actual interfaces of the proxy (with proxy.getClass().getInterfaces()[i].getClassLoader() for all i) shows that all interfaces are loaded with the system classloader. This causes the exception above. Doing some more experiments we experience that the problem does not occur all the time. Sometimes the actual proxy interfaces are as expected (the HibernateProxy interface is loaded by the system classloader and our interface was loaded by our custom classloader). We notice that each time the test failed the HibernateProxy was the first interface in the interface array stored in the proxy. Some experiments with the CGLIB (the Enhancer class) shows us that (if there is no superclass given) they use the classloader of the first passed interface as default classloader (compare method net.sf.cglib.proxy.Enhancer.getDefaultClassLoader()). Finally we find out that hibernate passes the proxy interfaces in an arbitrary order since they are using a HashSet for the proxy interfaces in the method org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PersistentClass persistentClass, Getter idGetter, Setter idSetter). This Hash set is passed to the method org.hibernate.proxy.pojo.cglib.CGLIB_ProxyFactory.postInstantiate(...). There it is simply converted to an Array (leading to a randomized order). As a workaround it is possible to patch the class org.hibernate.proxy.pojo.cglib.CGLIB_ProxyFactory and add reorganize the array if the HibernateProxy interface is the first one: this.interfaces = (Class[]) interfaces.toArray(NO_CLASSES); //----->PATCH<-------- if(this.interfaces.length > 1) { Class firstIfc = this.interfaces[0]; if(firstIfc.getName().startsWith("org.hibernate")) { this.interfaces[0] = this.interfaces[1]; this.interfaces[1] = firstIfc; System.err.println("Replace: " + firstIfc.getName() + " by " + this.interfaces[0].getName()); } } //-------------------- After applying this patch everything woks as expected. Compare with the discussion in: http://forum.hibernate.org/viewtopic.php?p=2334617#2334617 -- 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

13 years, 11 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3603) Hibernate custome classloader

by Behrang Javaherian (JIRA)

Hibernate custome classloader ----------------------------- Key: HHH-3603 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3603 Project: Hibernate Core Issue Type: New Feature Affects Versions: 3.3.0.GA Reporter: Behrang Javaherian We are trying to use hibernate in a OSGi like kind of environment. We have a code module that creates the session factory. We want to be able to add classes to session factory and recreated the session factory as needed. But hibernate is always using the current class loader which cause class cast exception if we try to add model classes from child bundles (which has their own class loader). To overcome this issue we had to patch the hibernate internal ReflectHelper and change the classForNameMethod to this: return PlugableClassFinder.getInstance().classForName(name); and here is the code for PlugableClassFinder class: public class PlugableClassFinder { private Set<ClassLoader> classLoaders = new HashSet<ClassLoader>(); public Class classForName(String name) throws ClassNotFoundException { try { ClassLoader contextClassLoader = Thread.currentThread().getContextClassLoader(); if ( contextClassLoader != null ) { return contextClassLoader.loadClass(name); } } catch ( Throwable t ) { } try { return Class.forName(name); } catch (ClassNotFoundException e) { } //now look into the registerred class loaders for (ClassLoader classLoader : classLoaders) { try { return classLoader.loadClass(name); } catch (ClassNotFoundException e) { } } throw new ClassNotFoundException("Cannot find class: " + name); } public void registerClassLoader(ClassLoader classLoader) { classLoaders.add(classLoader); } public void deregisterClassLoader(ClassLoader classLoader) { classLoaders.remove(classLoader); } private static final PlugableClassFinder instance = new PlugableClassFinder(); public static PlugableClassFinder getInstance() { return instance; } } Now every bundle will register its class loader with PlugableClassFinder class. Maybe hibernate should either allow plugging new class loaders to resolve classes or provide a hook o an interface that we can implement to replace the internal class resolving mechanism. For the moment our approach if working for us. Regards Behrang Javaherian http://www.beyondng.com -- 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

13 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3201) Provide osgi informations in hibernate MANIFEST.MF to be recognized as osgi-bundle

by Baptiste MATHUS (JIRA)

Provide osgi informations in hibernate MANIFEST.MF to be recognized as osgi-bundle ---------------------------------------------------------------------------------- Key: HHH-3201 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3201 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Reporter: Baptiste MATHUS Hi all, It would be great if the packaging of Hibernate could be done as osgi compatible jar. With little configuration, some plugins already exist to do it in simply. For informaiton, a jar can become osgi-compatible only by adding some properties inside the META-INF/MANIFEST.MF file. It lets the jar totally usable in a non-osgi environment, but let the jar be recognized as a "bundle" in an osgi-container (Eclipse, Apache Felix...). A good entrypoint for this, using maven2 to package, could be http://felix.apache.org/site/maven-bundle-plugin-bnd.html#MavenBundlePlug.... For example, Spring already did and their available jars on repo1.maven.org can be put directly in a eclipse/plugins directory and be recognized as a bundle/plugin. Cheers. -- 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

13 years, 11 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3441) Null pointer exception on org.hibernate.type.AbstractType.getHashCode(AbstractType.java:112)

by DEROUET (JIRA)

Null pointer exception on org.hibernate.type.AbstractType.getHashCode(AbstractType.java:112) -------------------------------------------------------------------------------------------- Key: HHH-3441 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3441 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.25., Oracle 10g, Spring 2.5.5 Reporter: DEROUET Priority: Blocker The issue concerns a problem already signaled in different forums, and I decided to report it in JIRA, because many people have this same problem and after days and days of work around, the solutions possibles are heavy or dangerous for a database integrity (for example remove a non-nullability constraint...). Here it is the problem a previous forum participant had perfectly summarized (see http://opensource.atlassian.com/projects/hibernate/browse/HHH-2326): A null pointer exception is thrown when: a) we have a composite key with one of the attributes of the key being an FK to another persistent class. b) The other persistent class has an ID field whose value is being generated. c) The instance of the other persistent class is transient (does not yet have an ID) We do not get the null pointer if we explicitly set the ID (generator=assigned) Here it is the failure trace: --> --> java.lang.NullPointerException at org.hibernate.type.AbstractType.getHashCode(AbstractType.java:112) at org.hibernate.type.AbstractType.getHashCode(AbstractType.java:120) at org.hibernate.type.EntityType.getHashCode(EntityType.java:279) at org.hibernate.type.ComponentType.getHashCode(ComponentType.java:189) at org.hibernate.engine.EntityKey.generateHashCode(EntityKey.java:104) at org.hibernate.engine.EntityKey.<init>(EntityKey.java:48) at org.hibernate.engine.StatefulPersistenceContext.getDatabaseSnapshot(StatefulPersistenceContext.java:240) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:189) at org.hibernate.event.def.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:512) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:80) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:507) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:499) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:495) at org.springframework.orm.hibernate3.HibernateTemplate$16.doInHibernate(HibernateTemplate.java:747) at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:419) at org.springframework.orm.hibernate3.HibernateTemplate.executeWithNativeSession(HibernateTemplate.java:374) at org.springframework.orm.hibernate3.HibernateTemplate.saveOrUpdate(HibernateTemplate.java:744) at eu.cec.argus.bcm.dao.businessContinuityEvent.BusinessContinuityEventDAOImpl.createBCEvent(BusinessContinuityEventDAOImpl.java:39) at eu.cec.argus.bcm.dao.businessContinuityEvent.BusinessContinuityEventDAOTest.testSaveBcEventAndRelatedMessagesAndMeetings(BusinessContinuityEventDAOTest.java:127) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.springframework.test.context.junit4.SpringTestMethod.invoke(SpringTestMethod.java:198) at org.springframework.test.context.junit4.SpringMethodRoadie.runTestMethod(SpringMethodRoadie.java:274) at org.springframework.test.context.junit4.SpringMethodRoadie$2.run(SpringMethodRoadie.java:207) at org.springframework.test.context.junit4.SpringMethodRoadie.runBeforesThenTestThenAfters(SpringMethodRoadie.java:254) at org.springframework.test.context.junit4.SpringMethodRoadie.runWithRepetitions(SpringMethodRoadie.java:234) at org.springframework.test.context.junit4.SpringMethodRoadie.runTest(SpringMethodRoadie.java:204) at org.springframework.test.context.junit4.SpringMethodRoadie.run(SpringMethodRoadie.java:146) at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.invokeTestMethod(SpringJUnit4ClassRunner.java:151) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:26) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:36) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Here they are my classes: @Entity @Table(name = "BCM_BC_EVENT") @IdClass(BusinessContinuityEvent.BusinessContinuityEventId.class) @SequenceGenerator(name = "Generator.BusinessContinuityEvent", sequenceName = "SEQ_BCM_BC_EVENT") public class BusinessContinuityEvent implements Serializable { @Embeddable public static class BusinessContinuityEventId implements Serializable { private static final long serialVersionUID = 3513299649110908676L; @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "Generator.BusinessContinuityEvent") @Column(name = "BCE_ID", insertable = false, updatable = false, nullable = false) private Long id; @ManyToOne(fetch = FetchType.LAZY, cascade = {CascadeType.PERSIST, CascadeType.REFRESH, CascadeType.MERGE}) @Cascade(org.hibernate.annotations.CascadeType.SAVE_UPDATE) @JoinColumn(name = "EVE_ID", referencedColumnName = "EVE_ID", nullable = false) private Event event; public BusinessContinuityEventId(){ } public BusinessContinuityEventId(Long id, Event event) { this.id = id; this.event = event; } public Long getId() { return id; } public void setId(Long id) { this.id = id; } public Event getEvent() { return event; } public void setEvent(Event event) { this.event = event; } @Override public boolean equals(Object obj) { if (obj instanceof BusinessContinuityEventId) { BusinessContinuityEventId other = (BusinessContinuityEventId) obj; return this.event.getId().equals(other.event.getId()) && this.id.equals(other.id); } return false; } @Override public int hashCode() { return this.event.getId().hashCode() ^ this.id.hashCode(); } } private static final long serialVersionUID = 5385009048448590115L; @Id private Long id; @Id private Event event; @OneToMany(fetch = FetchType.LAZY, cascade = {CascadeType.PERSIST, CascadeType.REFRESH, CascadeType.MERGE}) @Cascade(org.hibernate.annotations.CascadeType.SAVE_UPDATE) @JoinColumns({ @JoinColumn(name = "BCE_ID", referencedColumnName = "BCE_ID"), @JoinColumn(name = "EVE_ID", referencedColumnName = "EVE_ID")}) private List<Message> messages; public Long getId() { return id; } public void setId(Long id) { this.id = id; } public Event getEvent() { return event; } public void setEvent(Event event) { this.event = event; } public List<Message> getMessages() { return messages; } public void setMessages(List<Message> messages) { this.messages = messages; } } -- 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

13 years, 11 months

5
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3464) SimpleExpression.ignoreCase uses SQL server lowercase function for left part and JAVA lowercase function for right part of expression

by Vitaliy Tymchyshyn (JIRA)

SimpleExpression.ignoreCase uses SQL server lowercase function for left part and JAVA lowercase function for right part of expression ------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3464 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3464 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.6 Environment: tried with PostgreSQL Reporter: Vitaliy Tymchyshyn Priority: Minor When using SimpleExpression.ignoreCase (e.g. Restrictions.eq().ignoreCase, hibernate makes 'lower(field)=?' SQL expression, passing lowercased strings to '?' parameter. This may produce unpredictable results depending on Database server lower implementation and current JAVA locale (see JDK javadoc). For example, I've tried with '\u0130' character as in JDK JavaDoc. Postgresql produces: unhappy=> select lower('İ'); lower ------- i̇ (1 row) unhappy=> select char_length(lower('İ')); char_length ------------- 2 (1 row) While Java with default locale produces single-character 'i̇'. Of course the restriction will not work - it can not find 'İ' in database. I'd recommend to use 'lower(field)=lower(?)' to use same lower casing function for both parts of expression. -- 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

13 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2808) CLONE -Impossible to define caching for a subclass's collection in hibernate.cgf.xml

by Sebastien Blind (JIRA)

CLONE -Impossible to define caching for a subclass's collection in hibernate.cgf.xml ------------------------------------------------------------------------------------- Key: HHH-2808 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2808 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Affects Versions: 3.2.5 Environment: Hibernate 3.2.5 Sybase Reporter: Sebastien Blind Basically, hibernate allows to define <cache usage="transactional"/> inside the subclass mapping, i.e. <subclass name="SubClass" extends="BaseClass" discriminator-value="xxx"> <bag name="subClassLinks" lazy="false" inverse="true" batch-size="100"> <cache usage="transactional" region="xxx"/> <key column="xxx" not-null="true"/> <one-to-many class="xxx"/> </bag> <join table="xxx"> </join> </subclass> but it's not allowed to do the same using <collection-cache collection="subClass.myCollection" region="xxx" usage="transactional"/>. It throws: Exception in thread "main" org.hibernate.MappingException: Cannot cache an unknown collection: subClass.myCollection at org.hibernate.cfg.Configuration.setCollectionCacheConcurrencyStrategy(Configuration.java:1984) at org.hibernate.cfg.Configuration.parseSessionFactory(Configuration.java:1568) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1534) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1508) at org.hibernate.cfg.Configuration.configure(Configuration.java:1428) -- 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

13 years, 11 months

6
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2851) ParameterTranslationsImpl fails to correctly determine parameter type

by Alex Savitsky (JIRA)

ParameterTranslationsImpl fails to correctly determine parameter type --------------------------------------------------------------------- Key: HHH-2851 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2851 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Reporter: Alex Savitsky Priority: Minor For the conditions in the form "(:param IS NULL OR alias.someField = :param)", the HQL parses would not correctly determine the type of param, unless the conditions are swapped like "(alias.someField = :param OR :param IS NULL)". The reason is that NamedParamTempHolder classes are created for all parameter entries, in the order they appear in the query. The first occurrence (:param IS NULL) would have its expectedType set to null, and the second occurrence would use the param holder created by the first occurrence, without checking whether it can improve it in any way (which it can - the expectedType for second occurrence is correctly determined to be Long). Proposed fix would be to check for this particular condition, enhancing paramHolder if possible, with new information: old code: if ( paramHolder == null ) { paramHolder = new NamedParamTempHolder(); paramHolder.name = namedSpec.getName(); paramHolder.type = namedSpec.getExpectedType(); namedParameterMap.put( namedSpec.getName(), paramHolder ); } new code: if ( paramHolder == null ) { paramHolder = new NamedParamTempHolder(); paramHolder.name = namedSpec.getName(); paramHolder.type = namedSpec.getExpectedType(); namedParameterMap.put( namedSpec.getName(), paramHolder ); + } else if (paramHolder.getExpectedType() == null && namedSpec.getExpectedType() != null) { + paramHolder.type = namedSpec.getExpectedType(); } -- 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

13 years, 12 months

6
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2394) Support filter tag in subclass

by Welkin Hu (JIRA)

Support filter tag in subclass ------------------------------ Key: HHH-2394 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2394 Project: Hibernate3 Type: Improvement Components: core Versions: 3.0 beta 4 Reporter: Welkin Hu Assigned to: Steve Ebersole Fix For: 3.0 rc 1 According to a user: http://forum.hibernate.org/viewtopic.php?p=2229539#2229539 It's not possible to get a filter to apply to a subclass. This is Bad ;-) Steve, is that correct? -- 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
9
0 / 0

[Hibernate-JIRA] Created: (ANN-625) @OrderBy usage on a joined classes (when using join table) produces incorred SQL syntax.

by Dima Gutzeit (JIRA)

@OrderBy usage on a joined classes (when using join table) produces incorred SQL syntax. ---------------------------------------------------------------------------------------- Key: ANN-625 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-625 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Dima Gutzeit Please consider the following mapping : @ManyToMany(cascade = {CascadeType.PERSIST, CascadeType.MERGE}, fetch = FetchType.LAZY) @IndexColumn(name = "ListIndex") @JoinTable(name = "odp_rulemanipulatorjoin", joinColumns = @JoinColumn(name = "RoutingRuleId"), inverseJoinColumns = @JoinColumn(name = "ManipulatorComponentId")) @OrderBy(value = "priority asc") public List<RoutingManipulationComponent> getManipulators() { if (manipulators == null) { manipulators = new ArrayList<RoutingManipulationComponent>(); } return manipulators; } *********************************** @Entity(name = "RoutingManipulationComponent") @DiscriminatorValue("RoutingManipulationComponent") public abstract class RoutingManipulationComponent extends RoutingComponent implements Initializable { /** * Applies the manipulation to the given context. * * @param context the routing context to manipulate * @return true if any manipulation was applied, false if no manipulation * occurred */ public abstract boolean apply(RoutingContext context); } ****************************************** @Entity(name = "RoutingComponent") @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name = "RoutingComponentType", discriminatorType = DiscriminatorType.STRING) @DiscriminatorValue("RoutingComponent") @Table(name = "odp_routingcomponent") public abstract class RoutingComponent extends DialPlanProvisionalEntity { @Deprecated public RoutingComponent() { // blank } /** * @param name * @param description */ public RoutingComponent(String name, String description) { super(name, description); } } ******************************* @MappedSuperclass @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) public abstract class DialPlanProvisionalEntity extends ProvisionalEntity implements Initializable { private Long entityId; private boolean visible = true; private int priority; /** * Not for direct instantiation - this constructor also serves as public * constructor for hibernate, jax-ws etc. <br> */ @Deprecated public DialPlanProvisionalEntity() { this("(no name set)", "(no description set)"); } /** * @param name * @param description */ public DialPlanProvisionalEntity(String name, String description) { creationDate = GregorianCalendar.getInstance(); // now } @Id @GeneratedValue(strategy = GenerationType.AUTO) @Override public Long getId() { return entityId; } @Override public void setId(Long ruleCollectionId) { this.entityId = ruleCollectionId; } /** * @return Returns the priority. */ public int getPriority() { return priority; } /** * @param priority The priority to set. */ public void setPriority(int priority) { this.priority = priority; } @Override public boolean equals(Object o) { if (this == o) { return true; } if (o == null || Hibernate.getClass(this) != Hibernate.getClass(o)) { return false; } final ProvisionalEntity other = (ProvisionalEntity) o; return MiscUtils.equalOrBothNull(this.getName(), other.getName()); } @Override public int hashCode() { String name = this.getName(); return getClass().getName().hashCode() + 13 * name.hashCode(); } } The above mapping should use the "priority" field to the ordering. SQL that is produced is : select criteria0_.RoutingRuleId as RoutingR1_1_, criteria0_.CriteriaComponentId as Criteria2_1_, criteria0_.ListIndex as ListIndex1_, routingcri1_.id as id73_0_, routingcri1_.creationDate as creation3_73_0_, routingcri1_.description as descript4_73_0_, routingcri1_.lastModificationDate as lastModi5_73_0_, routingcri1_.name as name73_0_, routingcri1_.predefined as predefined73_0_, routingcri1_.status as status73_0_, routingcri1_.priority as priority73_0_, routingcri1_.visible as visible73_0_, routingcri1_.matcher_id as matcher25_73_0_, routingcri1_.criterion_id as criterion27_73_0_, routingcri1_.location_id aslocation26_73_0_, routingcri1_.RoutingComponentType as RoutingC1_73_0_ from odp_rulecriteriajoin criteria0_ left outer join odp_routingcomponent as routingcri1_ on criteria0_.CriteriaComponentId=routingcri1_.id where criteria0_.RoutingRuleId=1 order by odp_routingcomponent .priority asc It is wrong since not the table alias is used in the order by clause, but the real table name. Mysql fails with exception that odp_rulecriteriajoin.priority is unknown table. Changing the query to include "order by criteria0_.priority asc" returns the correct result. -- 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

9
22
0 / 0

[Hibernate-JIRA] Created: (HHH-2158) incorrect hql query on one-to-one with property-ref

by Sebastien Cesbron (JIRA)

incorrect hql query on one-to-one with property-ref ---------------------------------------------------- Key: HHH-2158 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2158 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: hibernate 3.2.0.ga with firebird 1.5.3 and jaybird 1.5.5 driver on windows XP Reporter: Sebastien Cesbron Attachments: testhib.zip I have a one-to-one relationship with property-ref between Master and Slave2. I want to find all Master instances that have a null Slave2 instance associated. To do so my query is select master from Master master where master.slave2 is null The sql generated is select master0_.oid as oid0_, master0_.libelle as libelle0_ from Master master0_ where master0_.oid is null which seems incorrect. It checks here Master instances with null id (config files are listed below). If I do my query like this select master from Master master where master.slave2.oid is null the generated sql is ok : select master0_.oid as oid0_, master0_.libelle as libelle0_ from Master master0_, Slave2 slave2x1_ where master0_.oid=slave2x1_.myMaster and (slave2x1_.oid is null) I have attached a small eclipse project that reproduces the problem This problem may-be related to the one I have submitted as issue HHH-1849 -- 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

6
7
0 / 0

[Hibernate-JIRA] Created: (HBX-948) org.hibernate.connection.DriverManagerConnectionProvider - problem closing pooled connection

by Sathish P (JIRA)

org.hibernate.connection.DriverManagerConnectionProvider - problem closing pooled connection -------------------------------------------------------------------------------------------- Key: HBX-948 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-948 Project: Hibernate Tools Issue Type: Bug Components: consoleconfiguration Affects Versions: 3.1.beta5 Environment: Eclipse Reporter: Sathish P WARN Finalizer org.hibernate.connection.DriverManagerConnectionProvider - problem closing pooled connection java.sql.SQLException: Io exception: Socket closed at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255) at oracle.jdbc.driver.T4CConnection.logoff(T4CConnection.java:481) at oracle.jdbc.driver.PhysicalConnection.close(PhysicalConnection.java:1203) at org.hibernate.connection.DriverManagerConnectionProvider.close(DriverManagerConnectionProvider.java:152) at org.hibernate.connection.DriverManagerConnectionProvider.finalize(DriverManagerConnectionProvider.java:142) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Unknown Source) at java.lang.ref.Finalizer.access$100(Unknown Source) at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source) -- 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

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2666) subselect fetching ignores max results

by James Roper (JIRA)

subselect fetching ignores max results -------------------------------------- Key: HHH-2666 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2666 Project: Hibernate3 Issue Type: Improvement Components: query-hql, query-sql Affects Versions: 3.2.1 Environment: Hibernate 3.2.1 HSQLDB 8.0 Reporter: James Roper Priority: Minor When maxResults is set for a query, the hibernate subselect fetching strategy ignores it. For example, I have a class entry, that has a list of comments, which are configured to use the subselect fetching strategy. You can see that in the original query, only the top ? results are fetched: select top ? entry0_.id as id0_, entry0_.title as title0_, entry0_.entry as entry0_, entry0_.time as time0_, entry0_.category_id as category5_0_ from Entry entry0_ order by entry0_.time desc But then when it does the sub select query to lazily load the comments, this is the query it runs: select comments0_.entry_id as entry5_1_, comments0_.id as id1_, comments0_.id as id1_0_, comments0_.time as time1_0_, comments0_.comment as comment1_0_, comments0_.author as author1_0_ from Comment comments0_ where comments0_.entry_id in ( select entry0_.id from Entry entry0_ ) order by comments0_.time desc So, it loads every single comment in the database, even though only the comments for the top ? entries are needed. Of course, if there was no order by clause on the first query, the sub select may not return the same results, so it should probably only do this when there is an order by clause in the first query, and it should make sure it includes the order by clause in the sub select. -- 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

6
12
0 / 0

[Hibernate-JIRA] Created: (ANN-609) Need a way to specify "unsaved-value" strategy using annotations

by Suji Suresh (JIRA)

Need a way to specify "unsaved-value" strategy using annotations ---------------------------------------------------------------- Key: ANN-609 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-609 Project: Hibernate Annotations Issue Type: Bug Environment: Hibernate 3.2.2, Hibernate-annotations 3.2.1 Reporter: Suji Suresh Hibernate has two ways of specifying a value for primary key: 1. Assign a value before handing it over to Hibernate 2. Have Hibernate generate the value before persisting In my project I have objects of both of the above specified types. In other words I assign value for the primary key for some the objects (lets call these objects "assigned") and for others I have Hibernate generate the value before persisting (lets call these objects "generated"). Since Hibernate annotations does not support "unsaved-value", I do not have a way of specifying "unsaved-value" strategy. While my "generated" objects work perfectly with Hibernate's default "unsaved-value" strategy, I see wrong (but expected) behaviour when I try to persist an "assigned" object that is already present in the database in that, I get StaleStateException instead of DataIntegrityViolationException -- 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

6
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3500) Hibernate fails to resolve the correct orderby column in SQL when using inheritance hierarchy

by Joonas Koivunen (JIRA)

Hibernate fails to resolve the correct orderby column in SQL when using inheritance hierarchy --------------------------------------------------------------------------------------------- Key: HHH-3500 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3500 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.0.GA Environment: Derby 10.4.2.0 (http://db.apache.org) Reporter: Joonas Koivunen I have an inheritance hierarchy: @Entity("abstractBaseClass") AbstractBaseClass - ConcreteClass1 - ConcreteClass2 - ConcreteClass3 AbstractBaseClass has: - @Id long id; - String name; @Entity("concreteClass1") ConcreteClass1 has a @OneToMany(mappedBy="concreteClass1") List<ConcreteClass2> @Entity("concreteClass2") ConcreteClass2 has a @OneToMany(mappedBy="concreteClass2") List<ConcreteClass3> and a reference to @ManyToOne ConcreteClass1. @Entity("concreteClass3") ConcreteClass3 has a reference to @ManyToOne ConcreteClass2. After adding a @OrderBy("name") annotation to the getter "List<ConcreteClass3> ConcreteClass2.getConcreteClass3s()" and afterwards accessing the association through an ConcreteClass2 instance I get: SELECT cc3_concrete.cc2_id, cc3_concrete.id, cc3_base.name, cc3_concrete.cc2_id AS cc2_id_2 FROM cc3 cc3_concrete INNER JOIN abstractBaseClass cc3_base ON cc3_concrete.id = cc3_base.id WHERE cc3_concrete.cc2_id = ? ORDER BY abstractBaseClass.name asc (I edited hibernate's naming of entities in SQL to be a bit more clearer). Ordering by "abstractBaseClass.name" causes the problem here; it's obvious that it should had been "cc3_base.name" but for some reason hib just uses the entityname.column_name in the SQL. Another strange thing is that the foreign key column "cc2_id" is being included twice in the results? It is included in the select wheter or not @OrderBy exists. Inheritance strategy used is javax.persistence.InheritanceType.JOINED. -- 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, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3300) HQL looks for property in wrong class and reports "could not resolve property"

by Cristian Bogdan (JIRA)

HQL looks for property in wrong class and reports "could not resolve property" ------------------------------------------------------------------------------ Key: HHH-3300 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3300 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.6 Environment: Hibernate 3.2.6.ga, mysql 5.0.37 Reporter: Cristian Bogdan could not resolve property: groupMembers of: projman.Project [SELECT it.project.color AS col1 FROM projman.Deficienta def JOIN def.item it WHERE exists (FROM it.project.participants grp JOIN grp.groupMembers p WHERE p=:principal ) )) ORDER BY it.end] the problem is, groupMembers is not a property of projman.Project, but a bag in projman,Principal. as soon as I replace the it.project.color projection with e.g. it.start (i.e. i don't make any other join with projman.Project), the query works. the original query is actually more complicated but i reduced my test to the above for simplicity. rewriting the query without subqueries is not an option. i paste the relevant (generated) mappings. <hibernate-mapping auto-import="false"> <class name="projman.Project" table="projman_Project_"> <id name="primaryKey" column="Project_"> <generator class="identity"/> </id> <property name="TS_modify" column="TS_modify_"/> <property name="TS_create" column="TS_create_"/> <property name="name"> <column name="name_" length="255"/> </property> <bag name="participants" table="projman_Project__participants_" cascade="all" inverse="false"> <key column="Project_"/> <many-to-many class="projman.Principal" column="Principal_"/> </bag> <many-to-one name="beneficiar" column="beneficiar_" cascade="all" class="projman.Company"/> <many-to-one name="generalDesigner" column="generalDesigner_" cascade="all" class="projman.Compa ny"/> <bag name="signExecution" table="projman_Project__signExecution_" cascade="all" inverse="false"> <key column="Project_"/> <many-to-many class="projman.Company" column="Company_"/> </bag> <property name="color"> <column name="color_" length="6"/> </property> </class> </hibernate-mapping> <hibernate-mapping auto-import="false"> <class name="projman.Principal" table="projman_Principal_"> <id name="primaryKey" column="Principal_"> <generator class="identity"/> </id> <property name="TS_modify" column="TS_modify_"/> <property name="TS_create" column="TS_create_"/> <property name="kind" column="kind_"/> <bag name="groupMembers" table="projman_Principal__groupMembers_" cascade="all" inverse="false"> <key column="Principal_"/> <many-to-many class="projman.Principal" column="Principal__"/> </bag> <property name="displayName"> <column name="displayName_" length="255"/> </property> </class> </hibernate-mapping> <hibernate-mapping auto-import="false"> <class name="projman.Deficienta" table="projman_Deficienta_"> <id name="primaryKey" column="Deficienta_"> <generator class="identity"/> </id> <property name="TS_modify" column="TS_modify_"/> <property name="TS_create" column="TS_create_"/> <many-to-one name="item" column="item_" cascade="all" class="projman.Item"/> <many-to-one name="firma" column="firma_" cascade="all" class="projman.Company"/> <bag name="alteFirme" table="projman_Deficienta__alteFirme_" cascade="all" inverse="false"> <key column="Deficienta_"/> <many-to-many class="projman.Company" column="Company_"/> </bag> <property name="amenda" column="amenda_"/> </class> </hibernate-mapping> <hibernate-mapping auto-import="false"> <class name="projman.Item" table="projman_Item_"> <id name="primaryKey" column="Item_"> <generator class="identity"/> </id> <property name="TS_modify" column="TS_modify_"/> <property name="TS_create" column="TS_create_"/> <many-to-one name="project" column="project_" cascade="all" class="projman.Project"/> <property name="type" column="type_"/> <bag name="toWhom" table="projman_Item__toWhom_" cascade="all" inverse="false"> <key column="Item_"/> <many-to-many class="projman.Principal" column="Principal_"/> </bag> <property name="subject"> <column name="subject_" length="255"/> </property> <property name="description" type="org.makumba.db.hibernate.TextUserType"> <column name="description_" sql-type="longtext"/> </property> <many-to-one name="creator" column="creator_" cascade="all" class="projman.Principal"/> <property name="creationDate" column="creationDate_"/> <property name="start" column="start_"/> <property name="end" column="end_"/> <bag name="events" inverse="true" cascade="none"> <key column="Item_"/> <one-to-many class="projman.Item__events"/> </bag> <bag name="attachments" table="projman_Item__attachments_" cascade="all" inverse="false"> <key column="Item_"/> <many-to-many class="projman.Document" column="Document_"/> </bag> </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

14 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-363) @OrderBy applied to collection property of derived class does not work properly when column used for ordering belongs to base class (using MySQL 5)

by Rich Eggert (JIRA)

@OrderBy applied to collection property of derived class does not work properly when column used for ordering belongs to base class (using MySQL 5) --------------------------------------------------------------------------------------------------------------------------------------------------- Key: EJB-363 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-363 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.GA Environment: MySQL 5.0.18, Hibernate Core 3.2.6, Hibernate EntityManager 3.3.2, and the MySQL5InnoDBDialect. Test run with Tomcat 6.0.16 (Sun JDK 1.6.0_06) and Spring Framework 2.5.3. Relying on Hibernate automatic DDL generation (hibernate.hbm2ddl.auto=update), which appears to be working properly. Reporter: Rich Eggert Attachments: SampleBase.java, SampleDerived.java, SampleServiceImpl.java I applied the (JPA) @OrderBy annotation to a collection of entities belonging to an entity class (named SampleDerived in the attached sample code) of the same type (i.e., the class has a one-to-many parent-child relationship to itself). The property name passed as the argument to the @OrderBy annotation refers to a property of the base class (named SampleBase in the example), which employs the "JOINED" inheritence strategy. When I attempted to access the collection of a persisted instance of the entity class (in the example, this is accomplished by calling SampleServiceImpl.createSample() followed by calling SampleServiceImpl.findChildren() against the return value), the following (root cause) exception is generated: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'SampleBase.timestamp' in 'order clause' com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936) com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2870) com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1573) com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1665) com.mysql.jdbc.Connection.execSQL(Connection.java:3176) com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1153) com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1266) org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93) org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) org.hibernate.loader.Loader.getResultSet(Loader.java:1787) org.hibernate.loader.Loader.doQuery(Loader.java:674) org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) org.hibernate.loader.Loader.loadCollection(Loader.java:1994) org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:36) org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:565) org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:63) org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1716) org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344) org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86) org.hibernate.collection.PersistentBag.iterator(PersistentBag.java:249) org.frecklepuppy.bb.service.impl.SampleServiceImpl.findChildren(SampleServiceImpl.java:52) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) $Proxy209.findChildren(Unknown Source) org.frecklepuppy.bb.ui.controllers.IndexController.listForums(IndexController.java:66) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.springframework.web.bind.annotation.support.HandlerMethodInvoker.doInvokeMethod(HandlerMethodInvoker.java:413) org.springframework.web.bind.annotation.support.HandlerMethodInvoker.invokeHandlerMethod(HandlerMethodInvoker.java:134) org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.invokeHandlerMethod(AnnotationMethodHandlerAdapter.java:310) org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter.handle(AnnotationMethodHandlerAdapter.java:297) org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:523) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:453) javax.servlet.http.HttpServlet.service(HttpServlet.java:690) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:359) org.springframework.security.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:109) org.springframework.security.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.ui.ExceptionTranslationFilter.doFilterHttp(ExceptionTranslationFilter.java:101) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.providers.anonymous.AnonymousProcessingFilter.doFilterHttp(AnonymousProcessingFilter.java:105) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.ui.rememberme.RememberMeProcessingFilter.doFilterHttp(RememberMeProcessingFilter.java:109) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.wrapper.SecurityContextHolderAwareRequestFilter.doFilterHttp(SecurityContextHolderAwareRequestFilter.java:91) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.ui.basicauth.BasicProcessingFilter.doFilterHttp(BasicProcessingFilter.java:172) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.ui.AbstractProcessingFilter.doFilterHttp(AbstractProcessingFilter.java:268) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:87) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.ui.SessionFixationProtectionFilter.doFilterHttp(SessionFixationProtectionFilter.java:68) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.securechannel.ChannelProcessingFilter.doFilterHttp(ChannelProcessingFilter.java:116) org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:174) org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:183) org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:138) I verified (using MySQL Administrator) that the SampleBase.timestamp column does, in fact, exist. According to the org.hibernate.SQL log, the offending SQL statement looks like this: select children0_.parent_id as parent2_1_, children0_.id as id1_, children0_.id as id5_0_, children0_1_.timestamp as timestamp5_0_, children0_.parent_id as parent2_6_0_ from SampleDerived children0_ inner join SampleBase children0_1_ on children0_.id=children0_1_.id where children0_.parent_id=? order by SampleBase.timestamp asc I believe the problem is that MySQL 5 requires that the alias for the base class table used in the FROM clause (children0_1_ in this case) be used in the ORDER BY clause, instead of the actual name of the base class table. After browsing various MySQL discussions, it appears this is new to MySQL 5 (versus 4 or earlier) and was done in order to be more standards compliant. It's unclear to me whether this affects Hibernate Core or is limited to EntityManager. I'll try to narrow down the problem further as time permits (which it isn't likely to do any time soon). -- 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, 1 month

8
15
0 / 0

[Hibernate-JIRA] Created: (HHH-3577) Wrong SQL in order by clause when using joined subclasses

by Hardy Ferentschik (JIRA)

Wrong SQL in order by clause when using joined subclasses --------------------------------------------------------- Key: HHH-3577 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3577 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Hardy Ferentschik Assignee: Steve Ebersole The changes for HHH-2802 seem to have broken the following tests in Annotations: * ManyToManyTest.testOrderByContractor() * OneToManyTest.testOrderByOnSuperclassProperty() Prior to the changes for HHH-2802 no table aliases where generated for in the SQL for these tests. Since it is generally a problem to generate the right table alias in case of joined subclasses there is a workaround in CollectionBinder.buildOrderByClauseFromHql() line 910 where the table name is explicitly set in the oder by clause. This workaround together with the changes for HHH-2802 now generate illegal SQL, eg: select contractor0_.EMPLOYER_ID as EMPLOYER1_1_, contractor0_.CONTRACTOR_ID as CONTRACTOR2_1_, contractor1_.id as id2_0_, contractor1_1_.fld_name as fld2_2_0_, contractor1_.hourlyRate as hourlyRate3_0_ from EMPLOYER_CONTRACTOR contractor0_ left outer join Contractor contractor1_ on contractor0_.CONTRACTOR_ID=contractor1_.id left outer join Employee contractor1_1_ on contractor1_.id=contractor1_1_.id where contractor0_.EMPLOYER_ID=? order by contractor1_.Employee.fld_name desc Hibernate: select contractor0_.EMPLOYER_ID as EMPLOYER1_1_, contractor0_.CONTRACTOR_ID as CONTRACTOR2_1_, contractor1_.id as id2_0_, contractor1_1_.fld_name as fld2_2_0_, contractor1_.hourlyRate as hourlyRate3_0_ from EMPLOYER_CONTRACTOR contractor0_ left outer join Contractor contractor1_ on contractor0_.CONTRACTOR_ID=contractor1_.id left outer join Employee contractor1_1_ on contractor1_.id=contractor1_1_.id where contractor0_.EMPLOYER_ID=? order by contractor1_.Employee.fld_name desc In this case 'contractor1_' is generated by the changes made for HHH-2802 whereas 'Employee' is added by the workaround. Note that even though Employee is not working for all databases, the generated alias is wrong and should be 'contractor1_1_. For now I commented out the failing tests since I cannot use the test skipping functionality in Annotations yet. -- 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, 1 month

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2828) criteria search by class throws org.hibernate.QueryException: Unsupported discriminator type null when mapping exists for this class

by jo desmet (JIRA)

criteria search by class throws org.hibernate.QueryException: Unsupported discriminator type null when mapping exists for this class ------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2828 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2828 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: hibernate 3.2.5, oracle 10g Reporter: jo desmet Attachments: src.zip when making a criteria based on a property of type class the query succeeds if this class is not mapped, the query building fails when this class is mapped within hibernate and has no discriminator e.g. code : Criteria l = session.createCriteria(SearchClass.class); l.add(Restrictions.eq("type", ClassWithNoMapping.class)); // SUCCESS java.util.List result = l.list(); l = session.createCriteria(SearchClass.class); l.add(Restrictions.eq("type", ClassWithMapping.class)); // EXCEPTION result = l.list(); exception is Hibernate: select this_.ID as ID0_0_, this_.name as name0_0_, this_.type as type0_0_ from SEARCHCLASS this_ where this_.type=? org.hibernate.QueryException: Unsupported discriminator type null at org.hibernate.loader.criteria.CriteriaQueryTranslator.getTypedValue(CriteriaQueryTranslator.java:499) at org.hibernate.criterion.SimpleExpression.getTypedValues(SimpleExpression.java:71) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getQueryParameters(CriteriaQueryTranslator.java:251) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:95) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) at Test.list(Test.java:40) at Test.main(Test.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) classes are attached, tables should exists but no data is required. Please also provide workaround on short term if possible -- 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, 2 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-188) Add an option to use JMS in a JTA tx (rather than the post TX work done right now)

by Emmanuel Bernard (JIRA)

Add an option to use JMS in a JTA tx (rather than the post TX work done right now) ---------------------------------------------------------------------------------- Key: HSEARCH-188 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-188 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Priority: Minor I think the main problem is ordering the hibernate flush and the JMS process. But I think the current PostTransactionWorkQueueSynchronization.beforeCompletion() suffers from the problem already. -- 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, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-5) Only index an entity when it's index properties have physically changed

by Emmanuel Bernard (JIRA)

Only index an entity when it's index properties have physically changed ----------------------------------------------------------------------- Key: HSEARCH-5 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-5 Project: Hibernate Search Type: New Feature Components: engine Reporter: Emmanuel Bernard Priority: Minor -- 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, 2 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-295) Generate the "right" FilterKey instance even on parameterized filters

by Emmanuel Bernard (JIRA)

Generate the "right" FilterKey instance even on parameterized filters --------------------------------------------------------------------- Key: HSEARCH-295 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-295 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Priority: Minor Rules around object equality are the most tricky. Not sure we can do a good job at it. -- 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, 2 months

2
4
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

14 years, 2 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

14 years, 2 months

7
25
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

14 years, 3 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2085) org.hibernate.event.def.DefaultLoadEventListener logs exception at info level

by Don Smith (JIRA)

org.hibernate.event.def.DefaultLoadEventListener logs exception at info level ----------------------------------------------------------------------------- Key: HHH-2085 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2085 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: Hibernate 3.2.0.cr2, MySQL 4.0.18 Reporter: Don Smith Priority: Minor Prior to schema generation, accessing a persistent object throws an exception, as expected. The org.hibernate.event.def.DefaultLoadEventListener logs the exception at the info level, which just adds noise to the application console, and prevents application exception handling (in my case it's valid if the table doesn't exist, so I just want to catch the exception and continue). This log statement should be removed, or moved to a debug or trace level, so it won't show up in normal execution. Code, from line 94 of org.hibernate.event.def.DefaultLoadEventListener: catch(HibernateException e) { log.info("Error performing load command", e); throw e; } -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3307) HQL query translation in real SQL ignores the dialect class

by Thomas Schilf (JIRA)

HQL query translation in real SQL ignores the dialect class ----------------------------------------------------------- Key: HHH-3307 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3307 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.6 Environment: dialect file with special JoinFragment and a "transformSelectString" step Reporter: Thomas Schilf We're using a special dialect class for a database. In the dialect is defined a own JoinFragment and a "transformSelectString" step. All workes fine by loading objects over a Criteria class. The generated SQL string is wrong by using named queries (HQL). The SQL string is in normal ANSI-SQL. The SqlGenerator and QueryTranslatorImpl classes from hibernate don't use the dialect class. -- 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, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (EJB-361) Query#setParameter(int position, Object value) wrong implementation

by Fabrice Daugan (JIRA)

Query#setParameter(int position, Object value) wrong implementation ------------------------------------------------------------------- Key: EJB-361 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-361 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.GA Reporter: Fabrice Daugan The Hibernate JPA javax.persistence.Query#setParameter(int position, Object value) implementation does not suit to the JPA specicafication. Indeed, the actual integer passed to the operation is converted to String by Hibernate and then used to find the named parameter. Please have a look to the folowing stack trace : java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException: org.hibernate.QueryParameterException: could not locate named parameter [1] at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:185) at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:240) at org.springframework.orm.jpa.JpaTemplate$9.doInJpa(JpaTemplate.java:316) To repoduce this error : -- 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, 3 months

3
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-22) Dynamic metadata mode

by Emmanuel Bernard (JIRA)

Dynamic metadata mode --------------------- Key: BVAL-22 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-22 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Priority: Minor Test how a dynamic reloading mode would work. Instead of caching metadata by ValidationFactory, reload as the data might have changed (annotations or XML) This can be a configuration setting. -- 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, 4 months

2
9
0 / 0

[Hibernate-JIRA] Created: (BVAL-44) Explore integration with Bean Validation APIs and a Rule engine

by Emmanuel Bernard (JIRA)

Explore integration with Bean Validation APIs and a Rule engine --------------------------------------------------------------- Key: BVAL-44 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-44 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Priority: Minor http://forum.hibernate.org/viewtopic.php?t=991847 If possible community driven. -- 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, 4 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2548) when "order by" a composit object, which may be null, the result list returns only when the composit objcts not null

by Yu Deng (JIRA)

when "order by" a composit object, which may be null, the result list returns only when the composit objcts not null -------------------------------------------------------------------------------------------------------------------- Key: HHH-2548 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2548 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.3 Environment: tomcat 5.5, eclipse3.2, jre1.5, postgreSQL8.1, hibernate3 and hibernate3.2 Reporter: Yu Deng Priority: Critical <hibernate-mapping package="com.grapevinecs.ams.domain.perbranch.inv"> <class name="InvItem"> <id name="id" column="id"> <generator class="hilo"/> </id> ... <many-to-one name="transferredDetails"/>  .... </class> (another mapping file) </hibernate-mapping>> <hibernate-mapping package="com.grapevinecs.ams.domain.perbranch.inv"> <class name="InvTransferDetails" > <id name="id" column="id"> <generator class="hilo"/> </id> <property name="returnedToICBC" type="com.grapevinecs.ams.dao.BooleanInteger" not-null="true"/> ... </class> </hibernate-mapping> Probelm: 1) The result returns 3000 records ---- select count(*) from InvItem c where upper(c.invType) LIKE '%D%' and c.invSeries.closed = '0' and c.branch =60551 order by c.transferredDetails.returnedToICBC asc, c.stamp asc,c.invNmbr asc 2) result List return size 0 by this query --- from InvItem c where upper(c.invType) LIKE '%D%' and c.invSeries.closed = '0' and c.branch =60551 order by c.transferredDetails.returnedToICBC asc, c.stamp asc,c.invNmbr asc 1) is correct but 2) is not correct. only when transferredDetails in InvItem not null be returned. in case 2), I have no transferredDetails not null. after I excuted the query 2), even I remove "c.transferredDetails.returnedToICBC asc", the result is still return nothing. -- 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, 4 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-321) FSSlaveDirectoryProvider incorrectly creates a subdirectory named 0

by Emmanuel Bernard (JIRA)

FSSlaveDirectoryProvider incorrectly creates a subdirectory named 0 ------------------------------------------------------------------- Key: HSEARCH-321 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-321 Project: Hibernate Search Issue Type: Bug Components: directory provider Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.1 I see a few areas where 0 is set on current. It probably comes from that. -- 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, 4 months

3
6
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 December 2008