December 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2380) Hibernate3.2.0 GA is JDK 1.3 Incompatible

by Alessandro Lazarotti (JIRA)

Hibernate3.2.0 GA is JDK 1.3 Incompatible ----------------------------------------- Key: HHH-2380 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2380 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: Hibernate 3.2.0 GA Reporter: Alessandro Lazarotti Priority: Minor The class org.hibernate.persister.entity.AbstractEntityPersister uses Boolean.valueOf, incompatible with JDK 1.3. Update for new Boolean. -- 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, 12 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3476) Generation of invalid SQL by HQL Delete

by Daniel Nunes (JIRA)

Generation of invalid SQL by HQL Delete --------------------------------------- Key: HHH-3476 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3476 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6, 3.1.3 Environment: MS SQL Server 2000, Hibernate 3.1.3 and Hibernate 3.2.6 GA Reporter: Daniel Nunes Attachments: grupo.rar, hibernate.cfg.xml Hibernate generates invalid DML command for HQL Delete statement. When doing: Integer vals[] = {1,3}; Query q = ugDAO.createQuery("delete UsuarioGrupo usuariorGrp"+ " where usuariorGrp.usuario.idusuario = :idUsr"+ " and usuariorGrp.grupo.idgrupo in (:idsGrupo)"+ " and usuariorGrp.grupo.cxpostal.idcxpostal = :idCx"); q.setParameterList("idsGrupo", vals); q.setInteger("idUsr", 77); q.setInteger("idCx", 2); It generates an SQL like this: Hibernate: delete from vanpix.dbo.usuario_grupo, vanpix.dbo.grupo grupo1_ where idusuario=? and (idgrupo in (? , ?)) and idcxpostal=? 17:26:22,406 DEBUG IntegerType:133 - binding '77' to parameter: 1 17:26:22,406 DEBUG IntegerType:133 - binding '1' to parameter: 2 17:26:22,406 DEBUG IntegerType:133 - binding '3' to parameter: 3 17:26:22,406 DEBUG IntegerType:133 - binding '2' to parameter: 4 17:26:22,453 WARN JDBCExceptionReporter:77 - SQL Error: 170, SQLState: 37000 17:26:22,453 ERROR JDBCExceptionReporter:78 - Line 1: Incorrect syntax near ','. Throwing the exception: Exception in thread "main" org.hibernate.exception.SQLGrammarException: could not execute update query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.hql.ast.exec.BasicExecutor.execute(BasicExecutor.java:84) at org.hibernate.hql.ast.QueryTranslatorImpl.executeUpdate(QueryTranslatorImpl.java:396) at org.hibernate.engine.query.HQLQueryPlan.performExecuteUpdate(HQLQueryPlan.java:259) at org.hibernate.impl.SessionImpl.executeUpdate(SessionImpl.java:1141) at org.hibernate.impl.QueryImpl.executeUpdate(QueryImpl.java:94) at com.pix.tests.HibernateTests.main(HibernateTests.java:37) Caused by: java.sql.SQLException: Line 1: Incorrect syntax near ','. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631) at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:505) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105) at org.hibernate.hql.ast.exec.BasicExecutor.execute(BasicExecutor.java:75) ... 5 more The HBMs are in the attachment. -- 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, 12 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1144) Weird Column Length problem - new length value in annotation being ignored

by Duncan Kinnear (JIRA)

Weird Column Length problem - new length value in annotation being ignored -------------------------------------------------------------------------- Key: HBX-1144 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1144 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.0.GA Environment: Tar file was hibernate-3.2.6.ga.tar. Glassfish version 2.0 ur2. PostgreSQL version 8.x (various) Reporter: Duncan Kinnear We are using Hibernate as our persistence layer with NetBeans 6.7.1, EJB3, Glassfish and PostgreSQL. We have almost 200 tables defined as EJB entities. We use annotations on the entities to define the tables/columns. As we are still in an early testing phase, we regularly drop all the tables in the database and use the Hibernate auto schema update to recreate them. Recently we changed the length of a standard field that appears in many of our tables. The column is called ID_ORDER and is defined in the entities using the following code: @Column(name = "ID_ORDER", length = STANDARD_ID_ORDER_LENGTH, nullable = false) private String idOrder; where STANDARD_ID_ORDER_LENGTH is defined as a public static final int in the superclass of these tables. This length used to be 20, but we increased this to 50, recompiled all the affected classes, dropped all the tables and redeployed. Now, on 2 developer machines this change worked correctly, with the new tables having their ID_ORDER columns all length 50. However, on the other 2 developer machines, one table (called FEED_TYPE) gets recreated with the ID_ORDER column with length 20. This also occurs when we deploy the resulting EAR file to another server running Glassfish. We have tried all sorts of things on these machines to try and 'fix' this. We have removed the column completely, recreated the table and it is still there! We have explicitly set the length in the annotation of the column of this one table and the length is always ignored. We have renamed the existing column and deployed, but the new column is always length 20. We have renamed the table and then recreated it - still wrong. We have even dropped the entire database and recreated it, but the length of 20 remains! We are pulling our hair out on this one, it just doesn't make any sense. Where is hibernate 'caching' the length definition of this one column in one table? -- 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, 12 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3787) org.hibernate.cfg.Configuration has non-Serializable member identifierGeneratorFactory

by Patrick Moore (JIRA)

org.hibernate.cfg.Configuration has non-Serializable member identifierGeneratorFactory -------------------------------------------------------------------------------------- Key: HHH-3787 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3787 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5 Environment: any Reporter: Patrick Moore Attachments: patch.txt //org.hibernate.cfg.Configuration (line 161): public class Configuration implements Serializable { // org.hibernate.cfg.Configuration (line 207): private DefaultIdentifierGeneratorFactory identifierGeneratorFactory; However DefaultIdentifierGeneratorFactory is not declared serializable. This patch makes DefaultIdentifierGeneratorFactory serializable. -- 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, 12 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4541) collection_valued_input_parameter not working in IN statement

by Farrukh Najmi (JIRA)

collection_valued_input_parameter not working in IN statement ------------------------------------------------------------- Key: HHH-4541 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4541 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0.Beta-1 Reporter: Farrukh Najmi 3.5.0-Beta1 of hibernate-entitymanager supports JPA 2.0. According to section 4.6.9 of the JPA 2.0 spec an IN statement can have a collection_valued_input_parameter: " in_expression ::= {state_field_path_expression | type_discriminator} [NOT] IN { ( in_item {, in_item}* ) | (subquery) | collection_valued_input_parameter } in_item ::= literal | single_valued_input_parameter " When I try the following query: SELECT DISTINCT Object(p) FROM org.freebxml.omar.jaxb.bindings.rim._4_0.PersonType p, org.freebxml.omar.jaxb.bindings.rim._4_0.AssociationType a WHERE a.sourceObject = :sourceObjectId AND p.id = a.targetObject AND a.type IN :typexxx with a List<String> value for collection_valued_input_parameter :typexxx I get the following unexpected error: Caused by: org.hibernate.hql.ast.QuerySyntaxException: unexpected token: : near line 1, column 226 [SELECT DISTINCT Object(p) FROM org.freebxml.omar.jaxb.bindings.rim._4_0.PersonType p, org.freebxml.omar.jaxb.bindings.rim._4_0.AssociationType a WHERE a.sourceObject = :sourceObjectId AND p.id = a.targetObject AND a.type IN :typexxx ] 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:94) 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:1585) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:121) -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4077) Misuse of NamingStrategy and logical column names in HbmBinder

by Emmanuel Bernard (JIRA)

Misuse of NamingStrategy and logical column names in HbmBinder -------------------------------------------------------------- Key: HHH-4077 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4077 Project: Hibernate Core Issue Type: Bug Components: metamodel Affects Versions: 3.3.2 Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-406) Removing cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory

by Amin Mohammed-Coleman (JIRA)

Removing cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory ------------------------------------------------------------------------------------ Key: HSEARCH-406 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-406 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.1.1.GA Environment: Mac OS 10.6 Reporter: Amin Mohammed-Coleman Priority: Minor Attachments: JMS.patch The patch provided removes the cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory. The patch also includes: 1) Validation in the initialize method of JMSBackendProcessorFactory to check whether connection factory and queue property is included 2) Created a JMSBackendProcessorParameter which encapsulates all the necessary info for JMSBackendProcessor 3) Updated JMSBackendProcessor to include transacted parameter -- 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

16 years

3
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-320) Hibernate Search conflicts with Spring's class path scanning

by Paul Middelkoop (JIRA)

Hibernate Search conflicts with Spring's class path scanning ------------------------------------------------------------ Key: HSEARCH-320 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-320 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.0.GA, 3.1.0.CR1 Reporter: Paul Middelkoop Hibernate Search conflicts with Spring's class path scanning. When Hibernate Search is on the classpath Spring throws an exception while reading annotation metadata. 3.1.0 Beta1 and 3.0.x versions had no problems. Stacktrace: Caused by: java.lang.ArrayIndexOutOfBoundsException: 50432 at org.springframework.asm.ClassReader.readUTF8(Unknown Source) at org.springframework.asm.ClassReader.accept(Unknown Source) at org.springframework.asm.ClassReader.accept(Unknown Source) at org.springframework.core.type.classreading.SimpleMetadataReader.getAnnotationMetadata(SimpleMetadataReader.java:55) at org.springframework.core.type.filter.AnnotationTypeFilter.matchSelf(AnnotationTypeFilter.java:68) at org.springframework.core.type.filter.AbstractTypeHierarchyTraversingFilter.match(AbstractTypeHierarchyTraversingFilter.java:55) at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.isCandidateComponent(ClassPathScanningCandidateComponentProvider.java:224) at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:182) at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:201) at org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:85) at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:69) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1255) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1245) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:92) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:507) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:398) -- 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

16 years

5
18
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-277) Adding Lucene Score

by Ulrich Vachon (JIRA)

Adding Lucene Score ------------------- Key: HSEARCH-277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-277 Project: Hibernate Search Issue Type: Improvement Reporter: Ulrich Vachon Priority: Minor Hello, Is it plans to add implicitly the score to bean via an annotation for example? In my bean, if I have a annoted property or method like : @Score private float score; HS will inject the score result after the query in my bean. Thank you, Ulrich -- 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

16 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3543) method org.hibernate.transaction.JDBCTransaction.notifyLocalSynchsBeforeTransactionCompletion "swallows" all exceptions occured inside it

by Roman (JIRA)

method org.hibernate.transaction.JDBCTransaction.notifyLocalSynchsBeforeTransactionCompletion "swallows" all exceptions occured inside it ----------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3543 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3543 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: MS Windows XP SP2, JDK 1.6.8, Eclipse 3.2.0 Reporter: Roman When using JBoss Envers any exceptions occured during saving data into version tables are swallowed by code block in class org.hibernate.transaction.JDBCTransaction (line 273): try { sync.beforeCompletion(); } catch (Throwable t) { log.error("exception calling user Synchronization", t); } Thereby, any exceptions occured in sync.beforeCompletion() will only be shown in log, but will not have any effect on application functionality So I have such behaviour: 1. Entity changes are saved in database by hibernate 2. Version tables for entities are empty, because, for example, of invalid column names 3. Transaction commits successfully. -- 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

16 years

5
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2009