April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4798) Add Envers manual to Hibernate core documentation

by Erik-Berndt Scheper (JIRA)

Add Envers manual to Hibernate core documentation ------------------------------------------------- Key: HHH-4798 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4798 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.5.0-Beta-3 Reporter: Erik-Berndt Scheper Now that Envers has been added to hibernate core, the Envers manual should be integrated into the Hibernate reference documentation. The Table of Contents of the latest version (3.5.0 Beta 3) does not even mention the Envers module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2510) override equals()/hashCode() in AliasToBeanResultTransformer

by Maxim Gordienko (JIRA)

override equals()/hashCode() in AliasToBeanResultTransformer ------------------------------------------------------------ Key: HHH-2510 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2510 Project: Hibernate3 Type: Improvement Versions: 3.2.2 Reporter: Maxim Gordienko AliasToBeanResultTransformer whould override equals()/hashCode() to allow convenient second level query caching. Now the only way is to maintain single transformer instance per bean class to allow query cache hit. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
9
0 / 0

[Hibernate-JIRA] Created: (ANN-663) @JoinColumn must be set for @AssociationOverride to work

by Bas van den Berg (JIRA)

@JoinColumn must be set for @AssociationOverride to work -------------------------------------------------------- Key: ANN-663 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-663 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate 3.2 , MySQL Reporter: Bas van den Berg Priority: Minor The following error is given when overiding the joincolumn which has not been set explicitly: Illegal attempt to define a @JoinColumn with a mappedBy association see http://forum.hibernate.org/viewtopic.php?t=960621&highlight= -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4011) ChainedPropertyAccessor is not serializable, which breaks caching to disk and replicated caches.

by Ryan Dearing (JIRA)

ChainedPropertyAccessor is not serializable, which breaks caching to disk and replicated caches. ------------------------------------------------------------------------------------------------ Key: HHH-4011 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4011 Project: Hibernate Core Issue Type: Bug Components: caching (L2), core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1 (not checked on 3.3.2) Reporter: Ryan Dearing ChainedPropertyAccessor is used by AliasToBeanResultTransformer. Since ChainedPropertyAccessor is not serializable any cacheable queries using AliasToBeanResultTransformer break during cache replication. For example, this query cannot be replicated or cached to disk: session.createQuery("select foo").setResultTransformer(new AliasToBeanResultTransformer(SimpleCount.class)).setCacheable(true).list(); A workaround is to make these queries not cacheable for now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3526) hbm2ddl.auto validate error on sequences in different schema

by Andres Galeano (JIRA)

hbm2ddl.auto validate error on sequences in different schema ------------------------------------------------------------ Key: HHH-3526 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3526 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1 GA & Oracle 9i Database Reporter: Andres Galeano Hello, My situation is that I have an persistent object and matching hbm that reference a table and sequence in a different oracle schema. When I set the "hibernate.hbm2ddl.auto" property to "validate", a hibernate error message claims that the sequence does not exist, although it does and is accessible. >From stepping through the code in class: org.hibernate.tool.hbm2ddl.DatabaseMetadata in method: public boolean isSequence(Object key) This code parses the 'key', in this case sequence name, by '.' and searches to see if the last element is contained in the list of sequences. So if I prefix my sequence name with the schema name it belongs to, it's ignored. This doesn't seem right to me. The code also seems to ignore the "schema" attribute of the "hibernate-mapping/class" element when validating sequence generators. To me this seems wrong as well. Since the 'list of sequences' is only for the current schema, at least in the case of Oracle9Dialect, the validate fails, even though the sequence does exist and seems to be properly specified to me. ------------------------------------------------------------ Excerpt from my hbm.xml file: ------------------------------------------------------------ ... ... <hibernate-mapping> <class name="bus.Accesspurpose" table="ACCESSPURPOSE" schema="WISH"> <id name="id" type="int"> <column name="ACCESSPURPOSEID" /> <generator class="sequence">  <param name="sequence">WISH.SEQ_ACCESSPURPOSEID</param> </generator> </id> ... ... ------------------------------------------------------------ Full stack trace. ------------------------------------------------------------ 2008-10-08 10:47:15,375 ERROR Thread-1 org.springframework.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SecurityManager' defined in class path resource [bus/wishdb-service-context.xml]: Cannot resolve reference to bean 'SecurityManagerDao' while setting bean property 'securityManagerDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SecurityManagerDao' defined in class path resource [db/wishdb-data-context.xml]: Cannot resolve reference to bean 'mySessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mySessionFactory' defined in class path resource [db/pp-app-data-context.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Missing sequence or table: WISH.SEQ_ACCESSPURPOSEID at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1172) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:940) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:437) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:400) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) 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.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SecurityManagerDao' defined in class path resource [db/wishdb-data-context.xml]: Cannot resolve reference to bean 'mySessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mySessionFactory' defined in class path resource [db/pp-app-data-context.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Missing sequence or table: WISH.SEQ_ACCESSPURPOSEID at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1172) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:940) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:437) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269) ... 41 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mySessionFactory' defined in class path resource [db/pp-app-data-context.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Missing sequence or table: WISH.SEQ_ACCESSPURPOSEID at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1260) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269) ... 53 more Caused by: org.hibernate.HibernateException: Missing sequence or table: WISH.SEQ_ACCESSPURPOSEID at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1127) at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:139) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:349) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1327) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:799) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:733) at org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractSessionFactoryBean.java:211) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1288) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1257) ... 62 more ----------------------------------------------------------- _________________ Thanks, - Andy See also the forums post: http://forum.hibernate.org/viewtopic.php?t=991326 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-604) There is no annotation to specify default value for a column

by Nicolae Bucalaete (JIRA)

There is no annotation to specify default value for a column ------------------------------------------------------------ Key: ANN-604 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-604 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Nicolae Bucalaete Priority: Critical In hibernate annotation you can't specify default value for a column. If you use xml files for mapping then you have this feature. I consider that this is a major problem with annotation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

15
17
0 / 0

[Hibernate-JIRA] Created: (HHH-3231) org.hibernate.id.enhanced.TableGenerator throws "IllegalArgumentException: alias not found: tbl" under Oracle

by Király Attila (JIRA)

org.hibernate.id.enhanced.TableGenerator throws "IllegalArgumentException: alias not found: tbl" under Oracle ------------------------------------------------------------------------------------------------------------- Key: HHH-3231 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3231 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6GA, Oracle 10g Reporter: Király Attila Attachments: hibernate_etg_ora.zip org.hibernate.id.enhanced.TableGenerator always throws the following exception if I want to save a new object to Oracle: java.lang.IllegalArgumentException: alias not found: tbl at org.hibernate.sql.ForUpdateFragment.<init>(ForUpdateFragment.java:36) at org.hibernate.dialect.Dialect.applyLocksToSql(Dialect.java:970) at org.hibernate.id.enhanced.TableGenerator.configure(TableGenerator.java:194) at org.hibernate.id.IdentifierGeneratorFactory.create(IdentifierGeneratorFactory.java:104) I attach an example to this case. The example is loosely based on the tutorial example, that comes with Hibernate. It contains a Person object that is saved to db using the enhanced.TableGenerator as id generator. To keep the zip small only the jars of jdbc driver are included, the jars needed from hibernate distribution are listed in lib/readme.txt. The zip also contains a modified TableGenerator that works with Oracle. This version was made by forum user stomp and more information about it can be read here: http://forum.hibernate.org/viewtopic.php?t=980933 It changes the 194th row of TableGenerator from this.query = dialect.applyLocksToSql( query, lockMap, CollectionHelper.EMPTY_MAP ); to this.query = dialect.applyLocksToSql( query, lockMap, Collections.singletonMap("tbl", new String[] {valueColumnName}) ); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

5
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-508) Support query on multiple fields

by Emmanuel Bernard (JIRA)

Support query on multiple fields -------------------------------- Key: HSEARCH-508 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-508 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-509) Add support for all() query and all except ones

by Emmanuel Bernard (JIRA)

Add support for all() query and all except ones ----------------------------------------------- Key: HSEARCH-509 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-509 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-414) Add support for a Lucene query builder using a fluent API

by Emmanuel Bernard (JIRA)

Add support for a Lucene query builder using a fluent API --------------------------------------------------------- Key: HSEARCH-414 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-414 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Emmanuel Bernard Fix For: 3.2.0.Beta3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-397) Allow classes to be lazily added to the configuration

by Emmanuel Bernard (JIRA)

Allow classes to be lazily added to the configuration ----------------------------------------------------- Key: HSEARCH-397 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-397 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Assignee: Sanne Grinovero Assigning Sanne to pick his interest ;) Infinispan needs a way to add new classes lazily, ie after the SearchFactory initialization. Today's initialization cannot ensure that because we assume a single thread inits everything before freezing the state and then support multiple thread. We need to explore the idea of making the configuration mutable but not suffering too much of the thread-safety implications. We also should allow to remove a class from the configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
16
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-487) Find why the zh-CN translation fails

by Emmanuel Bernard (JIRA)

Find why the zh-CN translation fails ------------------------------------ Key: HSEARCH-487 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-487 Project: Hibernate Search Issue Type: Bug Components: documentation Affects Versions: 3.2.0.Beta1 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-507) Rename exact() to keywords() and move fuzzy() and wildcard() back as suboperations of keywords()

by Emmanuel Bernard (JIRA)

Rename exact() to keywords() and move fuzzy() and wildcard() back as suboperations of keywords() ------------------------------------------------------------------------------------------------ Key: HSEARCH-507 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-507 Project: Hibernate Search Issue Type: Sub-task Components: query Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard http://pastebin.com/u7ucjRDR -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3771) Best pactice for equals implementation?

by Samppa Saarela (JIRA)

Best pactice for equals implementation? --------------------------------------- Key: HHH-3771 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3771 Project: Hibernate Core Issue Type: New Feature Components: core, documentation Reporter: Samppa Saarela When domain model contains even one lazy reference to an object, default equals fails when it's compared to a) the actual implementation returned by Session.get/load or b) other proxies (at least of different supertype). Overriding equals on a class that uses surrogate id is not that simple. However there is a simple solution to this problem: In domain class, override equals like this: public boolean equals(Object obj) { return this == getImplementation(obj); } public static Object getImplementation(Object obj) { if (obj instanceof HibernateProxy) { return ((HibernateProxy) obj).getHibernateLazyInitializer().getImplementation(); } else { return obj; } } This should result always in comparing object references of actual instances and thus preserve symmetry. It's understandable that you don't wan to publish that kind of getImplementation utility e.g. in Hibernate, but maybe you could support this more directly by implementing Hibernate.equals(Object o1, Object o2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5097) Bug in ParameterizedFunctionExpression with two or more parameters: IllegalArgumentException

by Max Hartmann (JIRA)

Bug in ParameterizedFunctionExpression with two or more parameters: IllegalArgumentException -------------------------------------------------------------------------------------------- Key: HHH-5097 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5097 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Environment: oracle 10g, hibernate 3.5 Reporter: Max Hartmann If you call CriteriaBuilder.function() respectively "ParameterizedFunctionExpression" with two or more arguments you get an IllegalArgumentException. I think the bug is here: protected void renderArguments(StringBuilder buffer, CriteriaQueryCompiler.RenderingContext renderingContext) { for ( Expression argument : argumentExpressions ) { buffer.append( ( (Renderable) argument ).render( renderingContext ) ); } } The arguments are not seperated by comma. Exception: Exception in thread "main" java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: unexpected token: : near line 1, column 37 [select TO_CHAR(generatedAlias0.date1:param0) from test.server.TestBean as generatedAlias0] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1166) at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1112) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:315) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:154) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:432) at test.server.TestApp.main(TestApp.java:28) Caused by: org.hibernate.hql.ast.QuerySyntaxException: unexpected token: : near line 1, column 37 [select TO_CHAR(generatedAlias0.date1:param0) from test.server.TestBean as generatedAlias0] at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:54) at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:47) at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:82) at org.hibernate.hql.ast.QueryTranslatorImpl.parse(QueryTranslatorImpl.java:284) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:182) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:98) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1760) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:297) ... 3 more Code: EntityManagerFactory factory = Persistence.createEntityManagerFactory("userDatabase"); EntityManager em = factory.createEntityManager(); CriteriaBuilder cb = em.getCriteriaBuilder(); CriteriaQuery<String> createQuery = cb.createQuery(String.class); Root<TestBean> from = createQuery.from(TestBean.class); Expression<String> param = cb.literal("DD.MM.YYYY"); createQuery.select(cb.function("TO_CHAR", String.class, from.get(TestBean_.date1), param)); List<String> resultList = em.createQuery(createQuery).getResultList(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-3908) Expose way to fully control fetching in native-sql queries in API

by Steve Ebersole (JIRA)

Expose way to fully control fetching in native-sql queries in API ----------------------------------------------------------------- Key: HHH-3908 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3908 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Steve Ebersole Fix For: 3.5 Currently, in order to fully control fetching in native-sql queries, users must revert to using a named sql query (at least the xml, not sure if the annotations variety supports as well). We alreasy have all the objects/contracts in place to handle this for the named queries, just need to clean-up and properly document them. The current API calls to deal with this are the overloaded SQLQuery#addJoin methods. Ideally I'd see these changed to return the representation of the join-fetch to be configured; but addJoin already defines a return : the query itself :( So probably we will need new methods like addFetch: 1) public JoinFetch addFetch(String alias, String ownerAlias, String ownerProperty) 2) public JoinFetch addFetch(String alias, String ownerAlias, String ownerProperty, LockMode lockMode) interface JoinFetch { public void addPropertyMapping(String propertyName, String sqlAlias); } This can be expanded to the "root returns" as well (currently the overloaded #addEntity methods): public RootReturn addRoot(String alias, Class entityClass) etc... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Example ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SQLQuery query = session.createSQLQuery( "select c.cust_id as cid, " + " c.cust_name as cname, " + " o.order_id as oid, " + " o.order_num as onum " + " from customer c " + " inner join orders o " + " on c.cust_id = o.cust_id" ); query.addRoot( "c", Customer.class ) .addPropertyMapping( "id", "cid" ) .addPropertyMapping( "name", "cname" ); query.addFetch( "o", "c", "orders" ) .addPropertyMapping( "id", "oid" ) .addPropertyMapping( "orderNumber", "onum" ); ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2350) 2nd level cache broken for inverse bidirectional one-to-many relation

by Burkhard Graves (JIRA)

2nd level cache broken for inverse bidirectional one-to-many relation --------------------------------------------------------------------- Key: HHH-2350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2350 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Database: MySQL, HSQL, ... (seems not to be important) Reporter: Burkhard Graves Attachments: testcase.tgz When using "inverse" one-to-many relations as described in "2.4.6.2.3. Bidirectional association with indexed collections" (http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.ht...) hibernate is wrong when activating 2nd level cache. See the attached example (unzip in /usr/local/hibernate-annotations-3.2.1.GA, testname=org.hibernate.test.annotations.invonetomany.InverseOneToManyTest). More details can be found here: http://forum.hibernate.org/viewtopic.php?t=969456 (and also in InverseOneToManyTest.java). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-3001) The NoopOptimizer needs to be synchronized

by Maciej Baranowski (JIRA)

The NoopOptimizer needs to be synchronized ------------------------------------------ Key: HHH-3001 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3001 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1, 3.2.6 Environment: 3.2.6, 3.2.4sp1, Oracle Reporter: Maciej Baranowski When SequenceStyleGenerator is used with Oracle it uses by default NoopOptimizer. The optimizer is not thread-safe and causes constraint violation errors while inserting data into 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

15 years, 9 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3279) create series of maven plugins offering functionality of the ant tools

by Steve Ebersole (JIRA)

create series of maven plugins offering functionality of the ant tools ---------------------------------------------------------------------- Key: HHH-3279 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3279 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3.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

15 years, 9 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3609) Invalid list re-ordering with IndexColumn and OneToMany association

by Martin Kovacik (JIRA)

Invalid list re-ordering with IndexColumn and OneToMany association ------------------------------------------------------------------- Key: HHH-3609 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3609 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1, Hibernate Tools 3.2.0, H2 database 1.0.69 Reporter: Martin Kovacik I want to map unidirectional OneToMany ordered list using annotations. My mapping is: public class Invoice { // ... @OneToMany(cascade = CascadeType.ALL) @JoinTable( name = "INVOICE_ITEM", joinColumns = {@JoinColumn(name = "invoice_id")}, inverseJoinColumns = {@JoinColumn(name = "item_id")} ) @Cascade(value = org.hibernate.annotations.CascadeType.DELETE_ORPHAN) @IndexColumn(name = "item_order") private List<Item> items = new ArrayList<Item>(); } The mapping of Item is not important here because I just want the association from Invoice to collection of Items to be unidirectional. The problem what hbm2ddl generates: create table INVOICE_ITEM ( invoice_id int8 not null, item_id int8 not null, item_order int4 not null, primary key (invoice_id, item_order), unique (item_id) ); alter table INVOICE_ITEM add constraint FK89837AD3EDA329D foreign key (item_id) references ITEM; alter table INVOICE_ITEM add constraint FK89837AD76A8E2D7 foreign key (invoice_id) references INVOICE; Another problem is how hibernate handles list re-ordering. If I want to change the item order (by manipulating invoice.items list) and then persist the changes hibernate tries to execute following sql: update INVOICE_ITEM set item_id=2 where invoice_id=1 and item_order=0 update INVOICE_ITEM set item_id=1 where invoice_id=1 and item_order=1 However this causes DB to complain about unique item_id constraint (which was generated by hibernate). IMHO hibernate should update just the item_order column. I think that this bug is related to ANN-679 (http://opensource.atlassian.com/projects/hibernate/browse/ANN-679). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2269) Many-to-one cascade fails with TransientObjectException if the inverse collection is marked CascadeType.DELETE_ORPHAN

by Edward Costello (JIRA)

Many-to-one cascade fails with TransientObjectException if the inverse collection is marked CascadeType.DELETE_ORPHAN --------------------------------------------------------------------------------------------------------------------- Key: HHH-2269 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2269 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2, 3.2.1 Environment: Using hibernate annotations. Reporter: Edward Costello Attachments: TestBidirectionalCascade.java When both a many-to-one (child) and it's inverse one-to-many collection (on parent) are cascading. Attempting to save a child directly and cascade the save to the parent throws a TransientObjectException if the parent's collection is mapped CascadeType.DELETE_ORPHAN. For Example, with the classes below: @Entity public class Parent { @OneToMany(mappedBy = "parent") @Cascade(value = {CascadeType.ALL, CascadeType.DELETE_ORPHAN}) Set<DeleteOrphanChild> deleteOrphanChildren; } @Entity public class DeleteOrphanChild { @ManyToOne @Cascade(value = CascadeType.ALL) Parent parent; } Calling session.save() with an instance of the parent will cascade the save to the child as expected. However, calling save on an instance of the child will throw the TransientObjectException below while attempting to cascade the save to the parent. org.hibernate.TransientObjectException: cascade.test.TestBidirectionalCascade$DeleteOrphanChild at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:216) at org.hibernate.collection.AbstractPersistentCollection.getOrphans(AbstractPersistentCollection.java:889) at org.hibernate.collection.PersistentSet.getOrphans(PersistentSet.java:51) at org.hibernate.engine.CollectionEntry.getOrphans(CollectionEntry.java:350) at org.hibernate.engine.Cascade.deleteOrphans(Cascade.java:336) at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:318) at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:185) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:160) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:108) at org.hibernate.engine.Cascade.cascade(Cascade.java:248) at org.hibernate.event.def.AbstractSaveEventListener.cascadeAfterSave(AbstractSaveEventListener.java:437) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:326) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:108) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:98) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:509) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:501) at org.hibernate.engine.CascadingAction$1.cascade(CascadingAction.java:134) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:213) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:157) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:108) at org.hibernate.engine.Cascade.cascade(Cascade.java:248) at org.hibernate.event.def.AbstractSaveEventListener.cascadeBeforeSave(AbstractSaveEventListener.java:412) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:261) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:108) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186) at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175) at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:537) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:525) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:521) If the DELETE_ORPHAN cascade is removed the save works fine. The attached test case runs against an in memory HSQLDB database. It contains 4 tests, the second test (testSaveChildDeleteOrphan) fails showing the above exception. The other three pass showing that cascading from the parent works and that cascading in both directions remove if the DELETE_ORPHAN cascade is removed. We've only tested this with annotations, we haven't tried to reproduce it using hibernate mapping files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4718) Select with subselect operands to a division gives NullPointerException on BinaryArithmeticOperatorNode

by Bruno Medeiros (JIRA)

Select with subselect operands to a division gives NullPointerException on BinaryArithmeticOperatorNode ------------------------------------------------------------------------------------------------------- Key: HHH-4718 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4718 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2, 3.2.7 Environment: Any Reporter: Bruno Medeiros I tried to perform the following query: --------------------------------------------------------------- select new map( e as estacao, ( ( select count(c) from Chamada c where 1 = 1 and c.estacao = e and c.data >= :dataInicial and c.data <= :dataFinal ) / ( select count(c2) from Chamada c2 where 1 = 1 and c.data >= :dataInicial and c.data <= :dataFinal ) ) as quantidade ) from Estacao e -------------------------------------------------------------- That gives the following atack trace: -------------------------------------------------------------- Exception in thread "main" java.lang.NullPointerException at org.hibernate.hql.ast.tree.BinaryArithmeticOperatorNode.getRightHandOperand(BinaryArithmeticOperatorNode.java:185) at org.hibernate.hql.ast.tree.BinaryArithmeticOperatorNode.initialize(BinaryArithmeticOperatorNode.java:20) at org.hibernate.hql.ast.HqlSqlWalker.prepareArithmeticOperator(HqlSqlWalker.java:1011) at org.hibernate.hql.antlr.HqlSqlBaseWalker.arithmeticExpr(HqlSqlBaseWalker.java:2783) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectExpr(HqlSqlBaseWalker.java:2006) at org.hibernate.hql.antlr.HqlSqlBaseWalker.aliasedSelectExpr(HqlSqlBaseWalker.java:2057) at org.hibernate.hql.antlr.HqlSqlBaseWalker.constructor(HqlSqlBaseWalker.java:2226) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectExpr(HqlSqlBaseWalker.java:1952) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectExprList(HqlSqlBaseWalker.java:1825) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectClause(HqlSqlBaseWalker.java:1394) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:553) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) ------------------------------------------------------------------ If I select the operands separately and do the division in Java code the query works perfectly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5148) Merge Hibernate Annotations reference documentation into Core

by Emmanuel Bernard (JIRA)

Merge Hibernate Annotations reference documentation into Core ------------------------------------------------------------- Key: HHH-5148 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5148 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Emmanuel Bernard Fix For: 3.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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5153) Convert non mapping sections form XML to Annotations or at least provide both solutions

by Emmanuel Bernard (JIRA)

Convert non mapping sections form XML to Annotations or at least provide both solutions --------------------------------------------------------------------------------------- Key: HHH-5153 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5153 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5064) OrderBy string getting dumped to console on session factory creation

by Shawn Clowater (JIRA)

OrderBy string getting dumped to console on session factory creation -------------------------------------------------------------------- Key: HHH-5064 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5064 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Reporter: Shawn Clowater Priority: Trivial I noticed the following when firing our app up the first time after updating to 3.5 final {code} > orderByFragment(order-by) > sortSpecification({sort specification}) > sortKeySpecification(sort key) > sortKey($PlaceHolder$.DISPLAY_ORDER) < sortKey(null) < sortKeySpecification(asc) > orderingSpecification(asc) < orderingSpecification(null) < sortSpecification(null) < orderByFragment(null) {code} Tracing through the debugger leads me to the AbstractCollectionPersister {code} if ( hasOrder ) { ColumnMapper mapper = new ColumnMapper() { public String[] map(String reference) { return elementPropertyMapping.toColumns( reference ); } }; sqlOrderByStringTemplate = Template.renderOrderByStringTemplate( collection.getOrderBy(), mapper, factory, dialect, factory.getSqlFunctionRegistry() ); } {code} the Template.renderOrder call eventually creates an OrderByFragmentTranslator which calls {code} GeneratedOrderByFragmentRenderer renderer = new GeneratedOrderByFragmentRenderer(); try { renderer.orderByFragment( parser.getAST() ); } {code} The GeneratedOrderByFragmentRenderer makes a call to the traceIn and traceOut methods of the antlr.TreeParser which seem to be dumping these values to System.out.println() I do notice that there is an OrderByFragmentRenderer that isn't used by the core code that seems to override these methods and log the output to log.trace(). Should the GeneratedOrderByFragmentRenderer be using that class instead? It's not that big of a deal but it is rather ugly at startup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

7
11
0 / 0

[Hibernate-JIRA] Created: (HHH-5162) Deprecate @Entity.mutable in favor of @Immutable

by Emmanuel Bernard (JIRA)

Deprecate @Entity.mutable in favor of @Immutable ------------------------------------------------ Key: HHH-5162 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5162 Project: Hibernate Core Issue Type: Improvement Components: annotations Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Priority: Trivial Fix For: 3.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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5155) Move Additional modules chapter from Annotations to Core probably in Appendix

by Emmanuel Bernard (JIRA)

Move Additional modules chapter from Annotations to Core probably in Appendix ----------------------------------------------------------------------------- Key: HHH-5155 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5155 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5145) Update pom to use the new distributationManagement information

by Strong Liu (JIRA)

Update pom to use the new distributationManagement information -------------------------------------------------------------- Key: HHH-5145 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5145 Project: Hibernate Core Issue Type: Task Components: build Reporter: Strong Liu Assignee: Strong Liu Priority: Minor Fix For: 3.5.x http://community.jboss.org/wiki/MavenGettingStarted-Developers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5115) Migrate Annotations and EntityManager documentation system to jdocbook's maven plugin (like core)

by Emmanuel Bernard (JIRA)

Migrate Annotations and EntityManager documentation system to jdocbook's maven plugin (like core) ------------------------------------------------------------------------------------------------- Key: HHH-5115 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5115 Project: Hibernate Core Issue Type: Task Components: annotations, entity-manager Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5149) Move mapping documentation from Annotations to Core

by Emmanuel Bernard (JIRA)

Move mapping documentation from Annotations to Core --------------------------------------------------- Key: HHH-5149 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5149 Project: Hibernate Core Issue Type: Sub-task Components: documentation Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.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

15 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5150) Update settings section to reflect merge from Annotations and Core documentation

by Emmanuel Bernard (JIRA)

Update settings section to reflect merge from Annotations and Core documentation -------------------------------------------------------------------------------- Key: HHH-5150 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5150 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5094) PersistenceUtilHelper cannot access non-public fields/methods (it should be able to)

by Philip Clay (JIRA)

PersistenceUtilHelper cannot access non-public fields/methods (it should be able to) ------------------------------------------------------------------------------------ Key: HHH-5094 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5094 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Environment: 3.5.0-Final. Any environment Reporter: Philip Clay Attachments: hibernate-entitymanager-bugreproduction.tgz PersistenceUtilHelper is only able to access public fields and public methods. As it is written, it cannot access non-public members. Internally, it incorrectly uses Class.getField(...) and Class.getMethod(...). It should use Class.getDeclaredField(...) and Class.getDeclaredMethod(...), so that it can see non-public members. I believe the use of getField and getMethod is not indented, because setAccessibility is the next call after that. Here is the code... {code} private static Object get(Object proxy, String property) { final Class<?> clazz = proxy.getClass(); try { try { final Field field = clazz.getField( property ); // only retrieves public fields!!! setAccessibility( field ); // if you really only wanted public fields, this call is unnecessary! return field.get( proxy ); } catch ( NoSuchFieldException e ) { final Method method = getMethod( clazz, property ); if (method != null) { setAccessibility( method ); // if you really only wanted public methods, this call is unnecessary! return method.invoke( proxy ); } ... } private static Method getMethod(Class<?> clazz, String methodName) { try { char string[] = methodName.toCharArray(); string[0] = Character.toUpperCase( string[0] ); methodName = new String( string ); try { return clazz.getMethod( "get" + methodName ); // only retrieves public methods!!! } catch ( NoSuchMethodException e ) { return clazz.getMethod( "is" + methodName ); // only retrieves public methods!!! } ... } private static void setAccessibility(Member member) { if ( !Modifier.isPublic( member.getModifiers() ) ) { //Sun's ease of use, sigh... ( ( AccessibleObject ) member ).setAccessible( true ); // This is dead code! The input member will always be public } } {code} Notice the call to setAccessibility. The call to setAccessibility shows that one assumes that the field retrieved from getField() (or method from getMethod()) could be non-public, which in fact it can't. All fields returned from getField will always be public (same for getMethod()). So, essentially the code inside the if statement in setAccessibility is dead code. I have attached a tarball containing a failing testcase that shows the incorrect behavior. Explode the tarball and run "mvn test" to reproduce the incorrect behavior. Also, within the tarball, I have included an svn diff for a proposed patch. See the README.txt file within the tarball for more info. I first noticed this problem when using hibernate validator to validate some protected members, but I narrowed it down to a problem in PersistenceUtilHelper. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4945) Replace all usages of EJB3TestCase with org.hibernate.ejb.test.TestCase

by Hardy Ferentschik (JIRA)

Replace all usages of EJB3TestCase with org.hibernate.ejb.test.TestCase ----------------------------------------------------------------------- Key: HHH-4945 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4945 Project: Hibernate Core Issue Type: Improvement Components: entity-manager Affects Versions: 3.5.0-CR-1 Reporter: Hardy Ferentschik Fix For: 3.5.x The setup in EJB3TestCase is really strange and we really want to have as many test as possible to derive from your main test base 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

15 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3765) Fill the "end revision" column with appropriate data in add/mod/del/collection work units

by Adam Warski (JIRA)

Fill the "end revision" column with appropriate data in add/mod/del/collection work units ----------------------------------------------------------------------------------------- Key: HHH-3765 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3765 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski In case of modifications, not only the "end revision" column should be set on new data, but also modified on existing data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3764) Add the "end-revision" column when generating metadata

by Adam Warski (JIRA)

Add the "end-revision" column when generating metadata ------------------------------------------------------ Key: HHH-3764 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3764 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski The column would only be added if the necessary setting is set to true. The column will have the same type as the revision number, but will be nullable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4568) Sybase - Test "BatchTest" fails due to "unexpected row count from update"

by Strong Liu (JIRA)

Sybase - Test "BatchTest" fails due to "unexpected row count from update" ------------------------------------------------------------------------- Key: HHH-4568 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4568 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.2.4.sp1 Environment: Sybase Reporter: Strong Liu Assignee: Strong Liu Fix For: 3.2.x, 3.3.x, 3.5, 3.3.0.GA, 3.2.4.sp1 The test "BatchTest" fails due to "org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1". The database server seems configured properly, as the "BatchUpdates" sample from jConnect 6 works correctly. The problem specifically occurs with a table that has a numeric column with precision (e.g. numeric(10,4)) Sybase does not thrown any SQLException when you try and persist a numeric value whose scale exceeds that defined on the column. Instead, it returns an updateCount of zero -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3579) Support for PostgreSQL UUID data type

by Olivier Van Acker (JIRA)

Support for PostgreSQL UUID data type ------------------------------------- Key: HHH-3579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3579 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.3.1 Reporter: Olivier Van Acker PostgreSQL has since version 8.3 UUID as data type nativly supported in the database. The only way to get this to work in Hibernate is to add <column name="id" sql-type="uuid"/> to your mappings file (or @columnDefinition via annotations) and create your own custom usertype (e.g. public class UUIDUserType implements UserType, Serializable {..} ) and map this to java.util.UUID worth mentioning is that java.util.UUID is only introduced in java 1.5 so there might be a backwards compatibility problem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

5
22
0 / 0

[Hibernate-JIRA] Created: (HHH-2277) bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop

by Emmanuel Bernard (JIRA)

bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop -------------------------------------------------------------------------------- Key: HHH-2277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2277 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2268) JDK Bug 5062759 Breaks Hibernate Introspection

by James Olsen (JIRA)

JDK Bug 5062759 Breaks Hibernate Introspection ---------------------------------------------- Key: HHH-2268 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2268 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.0.ga Environment: n/a Reporter: James Olsen Priority: Blocker Attachments: patch.txt Class#getDeclaredMethods() returns inherited methods - see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5062759 This can result in Hibernate failing to determine the correct return type for a method that overrides an inherited method and further constrains the return type. Behaviour is nondeterministic as it depends on the order of the returned array, e.g. public volatile java.lang.Object com.xxx.impl.CPMImpl.getId() // from interface implemented by superclass public volatile com.xxx.api.CPMId com.xxx.impl.CPMImpl.getId() // from superclass implementation public com.xxx.impl.CPMIdImpl com.xxx.impl.CPMImpl.getId() // local The patch checks if the method is 'volatile' and ignores it if it is. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

5
14
0 / 0

[Hibernate-JIRA] Created: (EJB-225) EntityManager.find infinite loop related to ANN-381

by John Schneider (JIRA)

EntityManager.find infinite loop related to ANN-381 --------------------------------------------------- Key: EJB-225 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-225 Project: Hibernate Entity Manager Type: Bug Environment: Hibernate Annotations 3.2.0.cr2 Hibernate EntityManager 3.2.0.cr2 Hibernate Core 3.2.0.cr4 Reporter: John Schneider Attachments: Test.zip I've tested the fix for ANN-381 and found that the improvement is not working correctly with the Entity Manager, specifically the find method. When calling the find method on a OneToMany collection mapped by a field in a primary key class, the Entity manager goes into an infinite loop of selecting records. Please note that a workaround is to replace the entity managers find method with a query, such as this: Query query = entityManager.createQuery("select c from Card c where c.id = :id"); query.setParameter("id", id); return (Card) query.getSingleResult(); However, this workaround doesn't work if you have other entities that relate to something like the Card entity, shown below. I'll expand on the example code from ANN-381 to show the problem of infinite looping when trying to load the related collection. @Entity public class Card implements Serializable { @Id private String id; @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.EAGER, mappedBy = "primaryKey.card") private Set<CardField> fields; public Card(String id) { this(); this.id = id; } Card() { fields = new HashSet<CardField>(); } public String getId() { return id; } public void setId(String id) { this.id = id; } public void addField(Card card, Key key) { fields.add(new CardField(card, key)); } } @Entity public class CardField implements Serializable { @EmbeddedId private PrimaryKey primaryKey; CardField(Card card, Key key) { this.primaryKey = new PrimaryKey(card, key); } CardField() { } } @Embeddable public class PrimaryKey implements Serializable { @ManyToOne(optional = false) private Card card; @ManyToOne(optional = false) private Key key; public PrimaryKey(Card card, Key key) { this.card = card; this.key = key; } PrimaryKey() {} } @Entity public class Key implements Serializable { @Id private String id; public Key(String id) { this.id = id; } Key() { } } >From what I can tell, this maps fine with the correct Hibernate libs and JBoss EJB Embeddable Alpha 9. However, the Entity Manager must be creating bad query code or something with similar results to having bad queries. I've testing with the following DAO: @Stateless public class CardDAOBean implements CardDAOLocal { @PersistenceContext private EntityManager entityManager; public void createCard(Card card) { entityManager.persist(card); } public Card findCard(String id) { return entityManager.find(Card.class, id); } public void createKey(Key key) { entityManager.persist(key); } } The Test class: public class EJBTest { private Card card; private Key key; public static void main(String[] args) { TestRunner.run(suite()); } public static junit.framework.Test suite() { TestSuite suite = new TestSuite("Test for ANN-381"); suite.addTest(new JUnit4TestAdapter(EJBTest.class)); // setup test so that embedded JBoss is started/stopped once for all // tests here. TestSetup wrapper = new TestSetup(suite) { protected void setUp() { startupEmbeddedJboss(); } protected void tearDown() { shutdownEmbeddedJboss(); } }; return wrapper; } @Before public void setup() { card = new Card("cardId"); key = new Key("keyId"); card.addField(card, key); } @Test public void persist() throws Exception { InitialContext ctx = getInitialContext(); CardDAOLocal CardDAOLocal = (CardDAOLocal) ctx.lookup("CardDAOBean/local"); CardDAOLocal.createKey(key); CardDAOLocal.createCard(card); Card card = CardDAOLocal.findCard(this.card.getId()); assertNotNull(card); } private static void startupEmbeddedJboss() { EJB3StandaloneBootstrap.boot(null); EJB3StandaloneBootstrap.scanClasspath(); } private static void shutdownEmbeddedJboss() { EJB3StandaloneBootstrap.shutdown(); } public static InitialContext getInitialContext() throws Exception { Hashtable properties = getInitialContextProperties(); return new InitialContext(properties); } private static Hashtable getInitialContextProperties() { Hashtable<String, String> props = new Hashtable<String, String>(); props.put("java.naming.factory.initial", "org.jnp.interfaces.LocalOnlyContextFactory"); props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); return props; } } Here's some relevant debugging output: Row insert: update CardField set card_id=? where card_id=? and key_id=? Row delete: update CardField set card_id=null where card_id=? and card_id=? and key_id=? One-shot delete: update CardField set card_id=null where card_id=? Static select for entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for action ACTION_MERGE on entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for action ACTION_REFRESH on entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for action ACTION_MERGE on entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for action ACTION_REFRESH on entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for action ACTION_MERGE on entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for action ACTION_REFRESH on entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for one-to-many entity.Card.fields: select fields0_.card_id as card2_1_, fields0_.key_id as key1_1_, fields0_.card_id as card2_1_0_, fields0_.key_id as key1_1_0_ from CardField fields0_ where fields0_.card_id=? When I call the findCard method in my EJB, the entity manager keeps looping through the select process several hundred times, and then dies from a stack overflow. Here's a sample of looping: DEBUG 17-09 21:17:18,328 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,343 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 0, globally: 0) DEBUG 17-09 21:17:18,343 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 1, globally: 1) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 1, globally: 1) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 2, globally: 2) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 2, globally: 2) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 3, globally: 3) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 3, globally: 3) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 4, globally: 4) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 4, globally: 4) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

8
23
0 / 0

[Hibernate-JIRA] Created: (HHH-5069) Fix annotation documentation wrt setup

by Steve Ebersole (JIRA)

Fix annotation documentation wrt setup -------------------------------------- Key: HHH-5069 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5069 Project: Hibernate Core Issue Type: Bug Components: annotations, documentation Affects Versions: 3.5.0-Final Reporter: Steve Ebersole Fix For: 3.5.x http://in.relation.to/Bloggers/Hibernate350FinalRelease#comment15080 The annotation guide seems to document incorrectly the steps getting started in terms of copying jars from the distribution to the developer project. Specificially it appears to call call for copying: * hibernate-annotations.jar (part of hibernate3.jar) * lib/hibernate-comons-annotations.jar (part of hibernate3.jar) * lib/hibernate-jpa-2.0-api.jar (actually under jpa/, not lib/) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5131) SchemaExport drop fails if constraint names change

by Strong Liu (JIRA)

SchemaExport drop fails if constraint names change -------------------------------------------------- Key: HHH-5131 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5131 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.3.2 Environment: PostgreSQL Reporter: Strong Liu Fix For: 3.3.x, 3.5.x for PostgreSQL dialect, it doesn't use cascade to drop tables, this may causes error when it drops the constraints. for example, there is a table A with a FK which name is "123456" but schemaUpdate uses a different FK name to drop it, then fails, then it tries to drop Table A, fails again :( HB-540 was reported a long ago, and Gavin added a comment "We can't apply this patch since older versions of Postgres don't support the cascade syntax." but I don't think it is still a problem( it was a comment added in 2003), as even the PostgreSQL 7.x support this syntax -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5032) Setting LockModeType.OPTIMISTIC_FORCE_INCREMENT defaults to only OPTIMISTIC

by Carlos Vara (JIRA)

Setting LockModeType.OPTIMISTIC_FORCE_INCREMENT defaults to only OPTIMISTIC --------------------------------------------------------------------------- Key: HHH-5032 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5032 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-CR-2 Environment: Hibernate Core 3.5.0-CR-2, Hibernate Validator 4.1 Snapshot, Spring 3.0.1, JPA2 Reporter: Carlos Vara Using EntityManager.lock(entity, LockModeType.OPTIMISTIC_FORCE_INCREMENT) doesn't change lock type, and version doesn't get updated on transaction commit. The following code: System.out.println("PRE lock mode: " + this.entityManager.getLockMode(an)); this.entityManager.lock(an, LockModeType.OPTIMISTIC_FORCE_INCREMENT); System.out.println("POST lock mode: " + this.entityManager.getLockMode(an)); Outputs: PRE lock mode: OPTIMISTIC POST lock mode: OPTIMISTIC Debugging AbstractLockUpgradeEventListener.upgradeLock, the reason is it doesn't upgrade it because previous lock mode is "READ" (whose level is 5), and OPTIMISTIC_FORCE_INCREMENT has level 4, so it doesn't trigger the update. I'm not sure about Hibernate's LockMode, but I think that OPTIMISTIC_FORCE_INCREMENT is a bit more restrictive than just OPTIMISTIC, so the locking type should be upgraded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

5
20
0 / 0

[Hibernate-JIRA] Created: (HHH-5078) JPA criteria query numeric expressions produce wrong result (due to wrong bracketing)

by Christoph Gerkens (JIRA)

JPA criteria query numeric expressions produce wrong result (due to wrong bracketing) ------------------------------------------------------------------------------------- Key: HHH-5078 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5078 Project: Hibernate Core Issue Type: Bug Components: entity-manager, query-criteria Affects Versions: 3.5.0-Final Environment: Hibernate-Core 3.5.0-Final, all database platforms Reporter: Christoph Gerkens The combination of quot and diff results in wrong SQL code. E.g.: (2 - 1) / 2 should be evaluated to 0.5 not 1.5 ( which is 2 - (1 / 2). JUnit 4 Test: @Test public void testJpaCriteriaApiQuoteAndDiff() { CriteriaBuilder cb = em.getCriteriaBuilder(); CriteriaQuery<Number> query = cb.createQuery(Number.class); query.from(SystemUser.class); // entity type doesn't matter, but must contain at least one entry for this test case. query.select( // (2 - 1) / 2 cb.quot( cb.diff( cb.literal(BigDecimal.valueOf(2.0)), cb.literal(BigDecimal.valueOf(1.0))), BigDecimal.valueOf(2.0))).distinct(true); Number result = em.createQuery(query).getSingleResult(); assertEquals(0.5d, result.doubleValue(), 0.1d); // (2 - 1) / 2 = 0.5 } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-5173) hql - average returns double but looses the decimal part

by Sébastien Peters (JIRA)

hql - average returns double but looses the decimal part -------------------------------------------------------- Key: HHH-5173 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5173 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Environment: Database driver: hsqldb OS: Mac-Os Hibernate: 3.5.0-Final Reporter: Sébastien Peters HQL: select avg(r.rating) from Review r for the values 2,2,2,1,2 it should return 1.8 instead of 1.0 type of rating: integer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
16
0 / 0

[Hibernate-JIRA] Created: (HHH-4966) Entity Manager bug with ParameterExpressionImpl

by jean-claude cote (JIRA)

Entity Manager bug with ParameterExpressionImpl ----------------------------------------------- Key: HHH-4966 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4966 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-CR-1 Reporter: jean-claude cote Emmanuel There seems to be a bug with the ParameterExpressionImpl class when rendering. If you create a criteria query using a ParameterExpression instance in multiple places in your query the rendering of this query will produce multiple pram0, param1, param2 for the same ParameterExpression instance. We fixed this bug by augmenting the RenderingContext interface with generateParameterName(Expression<?> exp). With this information the rendering context can give back the same jpaqlParameterName for the same ParameterExpression instance. All it has to do is do a lookup in its explicitParamtermapping map. Thanks Jean-Claude -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5178) Unit tests in org.hibernate.test.immutable fail on mssql and sybase due to keyword used for table and column name

by Gail Badner (JIRA)

Unit tests in org.hibernate.test.immutable fail on mssql and sybase due to keyword used for table and column name ----------------------------------------------------------------------------------------------------------------- Key: HHH-5178 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5178 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x, 3.6 Failing due to "plan" used for table and column name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3377) this time its h2 : foncusion of DECIMAL and NUMERIC column types

by Jan Baumann (JIRA)

this time its h2 : foncusion of DECIMAL and NUMERIC column types ----------------------------------------------------------------- Key: HHH-3377 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3377 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: H2 1.0.72, Hibernate 3.2.6 Reporter: Jan Baumann Analogous to HHH-2582 when trying to persist a BigDecimal object, hibernate throws a org.hibernate.HibernateException stating "Wrong column type in [...]. Found: decimal, expected: numeric" I checked the H2Dialect.java file, and as had been described for the MySQLDialect.java the following line was present : registerColumnType(Types.NUMERIC, "numeric"); Since H2 doesn't have a numeric type I tried the solution found for HHH-2582 and changed the line mentioned above to registerColumnType( Types.NUMERIC, "decimal($p,$s)" ); This seems to do the trick. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5006) hibernate.globally_quoted_identifiers=true and Annotations tests

by Stephan Palm (JIRA)

hibernate.globally_quoted_identifiers=true and Annotations tests ---------------------------------------------------------------- Key: HHH-5006 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5006 Project: Hibernate Core Issue Type: Bug Components: annotations, core Affects Versions: 3.5.0-CR-2 Environment: eclipse galileo jdk 1.6 Server library JBoss 6.0 M2 (actually I don`t think you need any of this information) Reporter: Stephan Palm If I use hibernate.globally_quoted_identifiers=true in order to quote all identifiers, then the mapping for column names breakes if I have a column with a @Column annotation but without a @Column(name=<COLUMN_NAME>). The mapping for the column name then turns out to be ``.　Which leads to problems when creating new tables. I was able to track the error back to {code} final String columnName = nameNormalizer.normalizeIdentifierQuoting( col.name() ); {code} from Ejb3Column.java. col.name() returns an empty string because the name was not explicitly set. nameNormalizer.normalizeIdentifierQuoting( col.name() ) then makes `` from the empty string. I was able to fix this problem by adding a guard to the nameNormalizer.normalizeIdentifierQuoting function: {code} if ( identifier.length() == 0) return null; {code} The function now looks like this: {code} public String normalizeIdentifierQuoting(String identifier) { if ( identifier == null ) { return null; } if ( identifier.length() == 0) return null; // Convert the JPA2 specific quoting character (double quote) to Hibernate's (back tick) if ( identifier.startsWith( "\"" ) && identifier.endsWith( "\"" ) ) { return '`' + identifier.substring( 1, identifier.length() - 1 ) + '`'; } // If the user has requested "global" use of quoted identifiers, quote this identifier (using back ticks) // if not already if ( isUseQuotedIdentifiersGlobally() && ! ( identifier.startsWith( "`" ) && identifier.endsWith( "`" ) ) ) { return '`' + identifier + '`'; } return identifier; } {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5171) Allow usage of standalone @JoinFormula annotation

by Sharath Reddy (JIRA)

Allow usage of standalone @JoinFormula annotation ------------------------------------------------- Key: HHH-5171 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5171 Project: Hibernate Core Issue Type: Improvement Components: annotations Affects Versions: 3.6 Reporter: Sharath Reddy Assignee: Sharath Reddy Fix For: 3.6 If there is a single-column join (based on formula) between 2 entities, it is overkill to wrap the @JoinFormula within a @JoinColumnsOrFormulas annotation: @ManyToOne @JoinColumnsOrFormulas( { @JoinColumnOrFormula(formula=@JoinFormula(value="SUBSTR(product_idnf, 1, 3)", referencedColumnName="product_idnf")) }) The above annotation is powerful, because it gives us the flexibility of using an arbitrary combination of columns and formulas for the join, but in this case it is redundant. If would be easier to just specify like this: @ManyToOne @JoinFormula(value="SUBSTR(product_idnf, 1, 3)", referencedColumnName="product_idnf")) }) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
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 April 2010