May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5192) Can't use group_concat in mysql without creating a custom function

by Douglas Ferguson (JIRA)

Can't use group_concat in mysql without creating a custom function ------------------------------------------------------------------ Key: HHH-5192 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5192 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.1 Environment: Linux, Mysql Reporter: Douglas Ferguson After upgrading we starting getting the exception below and had to register a "custom" function.. Caused by: org.hibernate.HibernateException: Unable to locate mapping for function named [group_concat] at org.hibernate.criterion.AggregateProjection.getFunction(AggregateProjection.java:93) at org.hibernate.criterion.AggregateProjection.getFunction(AggregateProjection.java:85) at org.hibernate.criterion.AggregateProjection.getTypes(AggregateProjection.java:64) at org.hibernate.criterion.ProjectionList.getTypes(ProjectionList.java:61) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getProjectedTypes(CriteriaQueryTranslator.java:362) at org.hibernate.loader.criteria.CriteriaJoinWalker.<init>(CriteriaJoinWalker.java:101) at org.hibernate.loader.criteria.CriteriaJoinWalker.<init>(CriteriaJoinWalker.java:83) at org.hibernate.loader.criteria.CriteriaLoader.<init>(CriteriaLoader.java:92) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1687) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:347) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5273) RowCountProjection long to int cast exception

by Pamir Erdem (JIRA)

RowCountProjection long to int cast exception --------------------------------------------- Key: HHH-5273 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5273 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.2 Environment: hibernate-core 3.5.2 Reporter: Pamir Erdem After we upgraded our hibernate.jar from 3.3.2 to 3.5.2 the methods which executes rowcount functions have started to throw long to cast exception. >From the source code of hibernate, it is clear that for the features which will be implemented in 3.6 some implementations are changed. #http://opensource.atlassian.com/projects/hibernate/browse/HHH-5138 In 3.3.2 {code:title=RowCountProjection.java|borderStyle=solid} public Type[] getTypes(Criteria criteria, CriteriaQuery criteriaQuery) throws HibernateException { return new Type[] { Hibernate.INTEGER }; } {code} In 3.5.2 {code:title=RowCountProjection.java|borderStyle=solid} return new Type[] { getFunction( criteriaQuery ).getReturnType( null, criteriaQuery.getFactory() ) }; {code} But the definitions of the rowcount functions in both versions in same in Dialect.java {code} static { STANDARD_AGGREGATE_FUNCTIONS.put( "count", new StandardSQLFunction("count") { public Type getReturnType(Type columnType, Mapping mapping) { return Hibernate.LONG; } public String render(List args, SessionFactoryImplementor factory) { if ( args.size() > 1 ) { if ( "distinct".equalsIgnoreCase( args.get( 0 ).toString() ) ) { return renderCountDistinct( args ); } } return super.render( args, factory ); } {code} By this minor change in 3.5.2 all the project tests which executes count sql function are failing by throwing class cast exception -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5098) AssertionFailure thrown when collection contains a parameterized type

by Kahli Burke (JIRA)

AssertionFailure thrown when collection contains a parameterized type --------------------------------------------------------------------- Key: HHH-5098 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5098 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Reporter: Kahli Burke Attachments: patch.txt The following exception is thrown when an entity exists with a collection containing a parameterized type: ERROR [AssertionFailure] an assertion failure occured (this may indicate a bug in Hibernate): org.hibernate.annotations.common.AssertionFailure: Fail to process type argument in a generic declaration. Type: class sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.getClassFromGenericArgument(AttributeFactory.java:836) at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:748) at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:723) at org.hibernate.ejb.metamodel.AttributeFactory.determineAttributeMetadata(AttributeFactory.java:518) at org.hibernate.ejb.metamodel.AttributeFactory.buildAttribute(AttributeFactory.java:93) at org.hibernate.ejb.metamodel.MetadataContext.wrapUp(MetadataContext.java:183) at org.hibernate.ejb.metamodel.MetamodelImpl.buildMetamodel(MetamodelImpl.java:66) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:83) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:883) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.jboss.jpa.builder.DefaultCEMFBuilder.build(DefaultCEMFBuilder.java:47) at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:316) For example if a field exists like: @OneToMany List<SomeEntity<SomeClass>> associatedList; I've attached a patch that includes a test case for the entity-manager project and a proposed fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5252) AttributeFactory needs more info in AssertionFailure

by Travis Stevens (JIRA)

AttributeFactory needs more info in AssertionFailure ---------------------------------------------------- Key: HHH-5252 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5252 Project: Hibernate Core Issue Type: Improvement Components: entity-manager Affects Versions: 3.5.2, 3.5.0-Final Environment: Hibernate version: 3.5.0-Final Reporter: Travis Stevens Priority: Trivial Attachments: tstevens-em.patch An exception is thrown that doesn't provide information about what member hibernate is asserting for. Attached is a patch that will include the associated Member object to the exception in order to provide some context. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5062) In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data

by Fabiano Cury (JIRA)

In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data ----------------------------------------------------------------------------------------------- Key: HHH-5062 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5062 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6 Environment: Linux / DB2 / version 3.2.6 and above Reporter: Fabiano Cury Attachments: issueHibernate.JPG When the flush method is called this method call the onFlush method of class DefaultFlushEventListener and then the method flushEverythingToExecutions(event). This method (flushEverythingToExecutions) call many times (loop) the method log.isDebugEnabled(). This cause a big overhead in this method. I suggest you to put an attribute in the method flushEverythingToExecutions(flushEverythingToExecutions(FlushEvent event, Boolean isDebugEnable) and verify this attribute before the loop for. Attached the print screen of profiling that help me to detect this issue. Tks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3045) Duplicated column aliases in scalar query

by Anderson Souza (JIRA)

Duplicated column aliases in scalar query ----------------------------------------- Key: HHH-3045 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3045 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.4SP1, 3.2.5GA Oracle 10g Reporter: Anderson Souza Priority: Critical Attachments: ddl-tables.sql, dominio.zip The HQL bellow works fine, but when I add a call to a funcion in the select clause the SQL generated has duplicated aliases and it generate error on query execution, because the query is paginated. {code} select a from Area a inner join fetch a.horarioPadrao left outer join fetch a.horarioTemporario as hrtemp {code} The SQL generated for this query is: {code} select * from ( select area0_.cod_local as cod1_15_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.des_local as des2_15_0_, area0_.sig_local as sig3_15_0_, area0_.flg_extinto as flg4_15_0_, horarioare1_.hr_hora_ini as hr2_6_1_, horarioare1_.hr_hora_fim as hr3_6_1_, horarioare1_.flg_fim_semana as flg4_6_1_, horarioare2_.hr_hora_ini as hr2_7_2_, horarioare2_.hr_hora_fim as hr3_7_2_, horarioare2_.flg_fim_semana as flg4_7_2_, horarioare2_.dat_ini_vigencia as dat5_7_2_, horarioare2_.dat_fim_vigencia as dat6_7_2_ from esq_fp.tb_local area0_ inner join tb_horario_local_padrao horarioare1_ on area0_.cod_local=horarioare1_.cod_area left outer join tb_horario_local_temporario horarioare2_ on area0_.cod_local=horarioare2_.cod_area where 1=1 order by area0_.sig_local ) where rownum <= ? {code} The scalar HQL query that generate duplicated column names is: {code} select a, count(*) from Area a inner join fetch a.horarioPadrao left outer join fetch a.horarioTemporario as hrtemp {code} The SQL generated is: {code} select * from ( select area0_.cod_local as col_0_0_, count(*) as col_1_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.cod_local as cod1_15_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.des_local as des2_15_0_, area0_.sig_local as sig3_15_0_, area0_.flg_extinto as flg4_15_0_, horarioare1_.hr_hora_ini as hr2_6_1_, horarioare1_.hr_hora_fim as hr3_6_1_, horarioare1_.flg_fim_semana as flg4_6_1_, horarioare2_.hr_hora_ini as hr2_7_2_, horarioare2_.hr_hora_fim as hr3_7_2_, horarioare2_.flg_fim_semana as flg4_7_2_, horarioare2_.dat_ini_vigencia as dat5_7_2_, horarioare2_.dat_fim_vigencia as dat6_7_2_ from esq_fp.tb_local area0_ inner join tb_horario_local_padrao horarioare1_ on area0_.cod_local=horarioare1_.cod_area left outer join tb_horario_local_temporario horarioare2_ on area0_.cod_local=horarioare2_.cod_area where 1=1 order by area0_.sig_local ) where rownum <= ? {code} As you can see the aliases cod1_6_1_ and cod1_7_2_ are repeated and this repetition breaks the paginated query, beacause the main query appears in the from clause. The HBM's and classes are attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4053) Incorrect SQL with substring for Firebird

by yeti the foot (JIRA)

Incorrect SQL with substring for Firebird ----------------------------------------- Key: HHH-4053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4053 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.3.1 Reporter: yeti the foot HQL query substring function generate incorrect SQL query for Firebird. In Firebird SQL query with substring has follow syntax: substring(str from 1 for 3). Generated ин Hibernate query looks like: substring(str, 1, 3). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2190) JDBCTransaction.isActive() should report false if jdbcContext.connection().isClosed()

by Jeffrey Bennett (JIRA)

JDBCTransaction.isActive() should report false if jdbcContext.connection().isClosed() ------------------------------------------------------------------------------------- Key: HHH-2190 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2190 Project: Hibernate3 Type: Bug Components: core Reporter: Jeffrey Bennett In error-handling routines, I use Transaction.isActive() to determine if it is 'safe' to perform Transaction.rollback(). If the Session has previously closed, Transaction.isActive() mis-reports that the transaction is still alive when it is not. I'll grant that the JavaDoc for isActive indicates it is the 'local transaction', not the underlying transaction, but since there is no way to delve into the underlying connection in the public API, that is really a cop-out. If you don't like the idea of modifying the behavior of isActive(), how about exposing a 'public Connection connection()' method that exposes the connection? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3058) When using native sql query and multiple selects with setMaxResults, Hibernate inserts the TOP statement in the first query

by Sean Blaes (JIRA)

When using native sql query and multiple selects with setMaxResults, Hibernate inserts the TOP statement in the first query --------------------------------------------------------------------------------------------------------------------------- Key: HHH-3058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3058 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4sp1, Microsoft SQL Server Reporter: Sean Blaes Priority: Minor When using a query similar to the following: DECLARE @SUB_TABLE TABLE( ID INT ) INSERT INTO @SUB_TABLE SELECT ID FROM FOO SELECT * FROM BAR INNER JOIN @SUB_TABLE ON ... Then if I call setMaxResults(100) on the query object. It inserts "TOP 100" in the first query, which isn't really what would be expected. Since the second SELECT actually consists of the data that will be returned, the TOP 100 statement should go there. I'd expect it's an easy fix. Just start your search for SELECT from the bottom rather than the top. However, I guess you have to make sure you're not hitting a subquery of a larger select either... I may try cooking up a patch this weekend for this if I can find the time, and I'll attach it to this issue if I do. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3405) Add support for Unicode aware MS SQL Server dialect

by Chris Larun (JIRA)

Add support for Unicode aware MS SQL Server dialect --------------------------------------------------- Key: HHH-3405 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3405 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.6 Reporter: Chris Larun Cf. http://jira.atlassian.com/browse/CONF-4786 for a description of the issue. http://forum.hibernate.org/viewtopic.php?t=941781&highlight=sqlserver+dia... for a possible solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2010