December 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3633) Envers ignores empty discriminator classes

by Mark Derricutt (JIRA)

Envers ignores empty discriminator classes ------------------------------------------ Key: HHH-3633 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3633 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.4 Reporter: Mark Derricutt 'lo I'm just working through updating our system to Hibernate 3.3 and the new maven based envers from trunk and am noticing that empty discriminator classes such as: @Entity @DiscriminatorValue("11004") @Versioned public class CountryGeo extends Geo { } are getting ignored by envers. This is manifested as the error "An audited relation to a non-audited entity" thrown from ToOneRelationMetadataGenerator. -- 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, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3673) overriding filters ina hiearchy

by Amir Pashazadeh (JIRA)

overriding filters ina hiearchy ------------------------------- Key: HHH-3673 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3673 Project: Hibernate Core Issue Type: Improvement Reporter: Amir Pashazadeh suppose: - class A and class B exist, and B extends A - both classes are mapped via annotations - class A has a @Filter with CONDITION1, it is a good idea to override the filter in class B, so a filter with just the same name can be applied on B with CONDITION2, so when querying B this filter applied. -- 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, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3672) Sybase - second(), minute(), hour(), and extract() cause GenericJDBCException

by Gail Badner (JIRA)

Sybase - second(), minute(), hour(), and extract() cause GenericJDBCException ----------------------------------------------------------------------------- Key: HHH-3672 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3672 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x, 3.3.x, 3.4 These functions are currently registered in SQLServerDialect. Moving them to SybaseDialect works for both Sybase and SQL Server. -- 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, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3668) Sybase does not support implicit conversion from 'VARCHAR' to 'INT' causes failing unit test

by Gail Badner (JIRA)

Sybase does not support implicit conversion from 'VARCHAR' to 'INT' causes failing unit test -------------------------------------------------------------------------------------------- Key: HHH-3668 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3668 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x, 3.3.x, 3.4 FooBarTest.testCollectionsInSelect() failing for sybase because it does not support implicit conversion from 'VARCHAR' to 'INT'. The same test passes using SQLServerDialect. -- 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, 6 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3670) Invalid test for str() for SQL Server and Sybase

by Gail Badner (JIRA)

Invalid test for str() for SQL Server and Sybase ------------------------------------------------ Key: HHH-3670 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3670 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x, 3.3.x, 3.4 The test for str() is invalid for SQL Server and Sybase because for those dialects: - there are 2 optional parameters to control number of characters for decimal plus decimal values (default is 0) and the total length of the field (default is 10) - value is right-justified The query currently used for ASTParserLoadingTest.testStr() uses the default for the optional values, so null is returned for Sybase and SQL Server. The query should be changed so that results are returned for all dialects, and checks are made that are appropriate to the dialect. -- 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, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3508) Sybase Dialect - Override supportsCascadeDelete to return "false"

by Juraci Paixao Krohling (JIRA)

Sybase Dialect - Override supportsCascadeDelete to return "false" ----------------------------------------------------------------- Key: HHH-3508 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3508 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: Hibernate from Branch_3_2_4_SP1_CP with Sybase 15. Reporter: Juraci Paixao Krohling It seems that Sybase doesn't supports "on cascade delete" [1][2]. Some tests under BulkManipulationTest fails due to this. A possible solution is to override supportsCascadeDelete in SybaseDialect to return "false". [1] http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15... [2] http://groups.google.com/group/sybase.public.ase.general/browse_thread/th... -- 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, 6 months

2
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-759) problem for mixxing setmaxresults and setlockmode

by areis (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-759?page=co... ] areis commented on HHH-759: --------------------------- I am facing the same problem as reported by Frederic Leitenberger (I also need to use ORDER BY, MAXROWS and FOR UPDATE in one query. ) . Is there an estimate of when there will be a solution? Thanks! > problem for mixxing setmaxresults and setlockmode > ------------------------------------------------- > > Key: HHH-759 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-759 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.0.2 > Environment: Client:windows2000 professional,jre1.4.2, oracle8client,eclipse3.1-RC3,hibernate-tools 3.0 alpha4a,JBossIDE1.5M1 > Server:Solaris 2.8, oracle 8.1.7 > Reporter: johnhua > Priority: Minor > > there is a problem for mixxing setmaxresults and setlockmode. > the problem is that "ORA-00904: invalid column name". > The error info is as the below: > Hibernate: select * from ( select idmapp0_.RI as col_0_0_ from PCTMNGT.IDMAP_P idmapp0_ where idmapp0_.STATUS=? ) where rownum <= ? for update of idmapp0_.RI > 14:21:54,076 DEBUG AbstractBatcher:AbstractBatcher.java:365 - preparing statement > 14:21:54,082 DEBUG AbstractBatcher:AbstractBatcher.java:285 - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) > 14:21:54,083 DEBUG AbstractBatcher:AbstractBatcher.java:403 - closing statement > 14:21:54,090 WARN JDBCExceptionReporter:JDBCExceptionReporter.java:71 - SQL Error: 904, SQLState: 42000 > 14:21:54,091 ERROR JDBCExceptionReporter:JDBCExceptionReporter.java:72 - ORA-00904: invalid column name > The source code is as the below: > //query an unused emid for new tone > query = av_session.createQuery("select v_idmap from IdmapP as v_idmap where v_idmap.status=:v_status"); > query.setCharacter("v_status",EMID_STATUS.UNUSED.charValue()); > query.setMaxResults(1); > query.setLockMode("v_idmap",LockMode.UPGRADE); > it = query.iterate(); > if( !it.hasNext() ) > { > tx.rollback(); > lv_err = "addRing::doAddRingFile: no unused EMID for new tone in idmap. toneid="+av_tone; > throw new InterfaceErrException(lv_err,INTERFACE_RETCODE.SYSTEM_ERR); > } -- 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, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3669) Ease sublassing of IdentityGenerator

by Mattias Jiderhamn (JIRA)

Ease sublassing of IdentityGenerator ------------------------------------ Key: HHH-3669 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3669 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.3.1 Reporter: Mattias Jiderhamn Priority: Minor Attachments: hibernate_IdentityGenerator_subclassing.patch We have a case where we subclass org.hibernate.id.IdentityGenerator. Unfortunately, we then also have to specifically declare sql-type in order to use automatic schema creation in our HSQLDB tests. This need could easily be removed with the supplied patch. -- 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, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3667) Problem in class Dialect

by Jorge Miguel da Silva e Sá (JIRA)

Problem in class Dialect ------------------------ Key: HHH-3667 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3667 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Jorge Miguel da Silva e Sá I have a problem with Hibernate. When I add one foreignKey Constraint in one table my application hang. When i debug the problem, I think I found a bug in this feature ( getAddForeignKeyConstraintString). When it does if ( !referencesPrimaryKey ) Not should not be if ( referencesPrimaryKey ) ? public String getAddForeignKeyConstraintString( String constraintName, String[] foreignKey, String referencedTable, String[] primaryKey, boolean referencesPrimaryKey) { StringBuffer res = new StringBuffer( 30 ); res.append( " add constraint " ) .append( constraintName ) .append( " foreign key (" ) .append( StringHelper.join( ", ", foreignKey ) ) .append( ") references " ) .append( referencedTable ); if ( !referencesPrimaryKey ) { res.append( " (" ) .append( StringHelper.join( ", ", primaryKey ) ) .append( ')' ); } return res.toString(); } -- 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, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2629) Enable ordering by association paths

by Jörg Heinicke (JIRA)

Enable ordering by association paths ------------------------------------ Key: HHH-2629 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2629 Project: Hibernate3 Issue Type: Patch Components: query-criteria Affects Versions: 3.2.4.sp1 Reporter: Jörg Heinicke In Hibernate's criteria API ordering is not possible on association properties without explicitly creating aliases. This also only works on one level, not recursively as it would be needed in the following example. Criteria criteria = session.createCriteria(Account.class); Criteria pCriteria = criteria.createCriteria("person"); pCriteria.add(Example.create(person)); pCriteria.createCriteria("company"); criteria.addOrder(Order.asc("person.company.name")); return criteria.list(); I have changed CriteriaQueryTranslator in a way that it first searches the aliasCriteriaMap, second the associationPathCriteriaMap. And the key used for the search is no longer StringHelper.root( propertyName ); but StringHelper.qualifier( propertyName ); >From what I understand this can't break anything since it has always only worked with one '.' in the path. For those cases the key stays the same. This implementation is still not perfect since 1. you need to create criteria in advance 2. you can't switch between alias and actual association path. The best would probably be to walk the path recursively. -- 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, 6 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2008