February 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HCANN-34) @Index Columns in @MappedSuperClasses don't work

by Mathias Reem (JIRA)

@Index Columns in @MappedSuperClasses don't work ------------------------------------------------ Key: HCANN-34 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-34 Project: Hibernate Commons Annotations Issue Type: Bug Affects Versions: 3.2.0 Environment: hibernate-commons-annotations-3.2.0.jar hibernate-core-3.6.0.jar postgres java 1.6 Reporter: Mathias Reem Indices in MappedSuperclass are not created in each child Entity, but only in one of them, as index names are global (at least in postgres), for the other Entites I get errors: 10:00:17 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate]: Unsuccessful: create index hash on B (hash) 10:00:17 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate]: ERROR: relation "hash" already exists {code:title=Root.java|borderStyle=solid} @MappedSuperclass abstract class Root { @Column(nullable = false, unique = true) @Index(name = "hash") private String hash; @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Long id; // Getter, Setter, ... } {code} {code:title=A.java|borderStyle=solid} @Entity public class A extends Root { // Getter, Setter, ... } {code} {code:title=B.java|borderStyle=solid} @Entity public class B extends Root { // Getter, Setter, ... } {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

14 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5918) generate schema update script does not respect default schema and default catalog when querying foreign key contraints

by Christoph Weißenborn (JIRA)

generate schema update script does not respect default schema and default catalog when querying foreign key contraints ---------------------------------------------------------------------------------------------------------------------- Key: HHH-5918 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5918 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.1, 3.6.0, 3.5.6, 3.5.5, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final, 3.3.2, 3.3.1, 3.3.0.SP1, 3.2.7, 3.2.6, 3.2.5, 3.2.4.sp1, 3.2.3, 3.2.2, 3.2.1, 3.2.0.ga, 3.1.3, 3.1.2, 3.1.1, 3.1, 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0 final Reporter: Christoph Weißenborn Priority: Critical When starting session factoring with mode "allow schema update" the database is inspected. Table structures are queried within correct schema and catalog. But foreign key constraints and indexes were not. If a index/foreign key is defined in another schema at the same sql server, the index/foreign key is not created in the current schema. The fix is very easy. org.hibernate.cfg.Configuration (revision 20769), method generateSchemaUpdateScript(Dialect, DatabaseMetadata): In line 1174 und 1175 use default schema und catalog if not specified for the table. This metadata is used for table structures. Copy these 2 lines to 1217 und 1218 where the default schema and catalog is _not_ used when not specified for the table. This metadata is used for foreign key and indexes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3123) NullPointerException on invalid HQL query with an extra brace

by Geoffrey De Smet (JIRA)

NullPointerException on invalid HQL query with an extra brace ------------------------------------------------------------- Key: HHH-3123 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3123 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Reporter: Geoffrey De Smet Priority: Trivial This query: "select p from IndividueleRekeningKasPO p left join fetch p.irTotalen inner join fetch p.toegangIndividueleRekeningKas tirkas where tirkas.authorityRef in (:authorityref)) and p.soort = :soort and p.id > 0" gives a NPE. The strange thing is that this query executes: "select p from IndividueleRekeningKasPO p left join fetch p.irTotalen inner join fetch p.toegangIndividueleRekeningKas tirkas where tirkas.authorityRef in (:authorityref)) and p.id > 0" both are invalid, because there is a closing brace to much in "(:authorityref))". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5920) in org.hibernate.mapping.PersistentClass some 2 performance issues can be fixed

by Christoph Weißenborn (JIRA)

in org.hibernate.mapping.PersistentClass some 2 performance issues can be fixed ------------------------------------------------------------------------------- Key: HHH-5920 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5920 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.6.1, 3.5.5, 3.3.2, 3.2.7, 3.1.3, 3.0.5 Reporter: Christoph Weißenborn Attachments: org.hibernate.mapping.persistentclass.patch 3 performance issues in org.hibernate.mapping.PersistentClass: 1. The mappedClass is loaded again and again calling ReflectHelper.classForName(className). The mapped class is not changed so it should be hold as member variable. 2. Method getProperty(String, Iterator) uses a MappingException which is ignored in getRecursiveProperty(String, Iterator). This makes the recursion more expensive than required. 3. Method getProperty calls StringHelper.root( propertyName ) for every property. Simply change the while in if do while. A fix is provided as 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

14 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5919) criteria loader runs into ArrayIndexOutOfBoundsException caused by wrong condition handling for column span zero

by Christoph Weißenborn (JIRA)

criteria loader runs into ArrayIndexOutOfBoundsException caused by wrong condition handling for column span zero ---------------------------------------------------------------------------------------------------------------- Key: HHH-5919 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5919 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.1, 3.5.4, 3.3.2, 3.2.7, 3.1.2, 3.0.5 Reporter: Christoph Weißenborn Attachments: org.hibernate.loader.criteria.criterialoader.patch Retriving results from a query with a last column with zero column span we run into ArrayOutOfBoundsException. An easy fix: org.hibernate.loader.criteria.CriteriaLoader (revision 20078) method getResultColumnOrRow(Object[], ResultTransformer, ResultSet, SessionImplementor) In line 143 condition ">" should change to "!=". The variable pos is not a valid index for columnAlias when numColumns (=column span) is 0. ArrayHelper.slice handles condition numColumns zero correctly. Alternative workaround: Change how the query is built. The last column should be at another position in the query. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5019) @TableGenerator throws Unsupported exception - error performing isolated work

by Rohini (JIRA)

@TableGenerator throws Unsupported exception - error performing isolated work ----------------------------------------------------------------------------- Key: HHH-5019 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5019 Project: Hibernate Core Issue Type: Bug Affects Versions: 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, 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2, 3.2.1 Environment: Hibernate Core 3.3.1, MySQL, Websphere 6.1 with EJB3.0 Feature pack Reporter: Rohini While implementing GenerationType.TABLE strategy with Hibernate as the persistence provider, id generation throws javax.persistence.PersistenceException: org.hibernate.HibernateException: error performing isolated work [3/18/10 14:40:41:533 IST] 0000002d SystemErr R at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:614) -------------------------------------------------------------- 3/18/10 14:40:41:533 IST] 0000002d SystemErr R Caused by: org.hibernate.HibernateException: error performing isolated work at org.hibernate.engine.transaction.Isolater$JtaDelegate.delegateWork(Isolater.java:166) at org.hibernate.engine.transaction.Isolater.doIsolatedWork(Isolater.java:64) at org.hibernate.engine.TransactionHelper.doWorkInNewTransaction(TransactionHelper.java:74) at org.hibernate.id.MultipleHiLoPerTableGenerator.generate(MultipleHiLoPerTableGenerator.java:210) Looking at the Isolater.doIsolatedWork( work, session );, implementation try { // First we need to suspend any current JTA transaction and obtain // a JDBC connection surroundingTransaction = transactionManager.suspend(); if ( log.isDebugEnabled() ) { log.debug( "surrounding JTA transaction suspended [" + surroundingTransaction + "]" ); } This happnes only with WebsphereExtendedTransactionManagerLookup as the hibernate.transaction.manager_lookup_class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5912) bidirectional relations: inverse end is not persistent

by Thomas Käfer (JIRA)

bidirectional relations: inverse end is not persistent ------------------------------------------------------ Key: HHH-5912 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5912 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.6.1 Environment: Hibernate 3.6.1, Microsoft SQL Server 2005 Reporter: Thomas Käfer It seems to me, as if it is not possible to make the reverse side of an relation persistent. So if one adds/remove an entity to/from the collection on the reverse side and then saves the reverse end entity, the relation is not persisted. This is a feature that I would require very much. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5904) Deploy just testing artifacts from hibernate-core, not all tests

by Steve Ebersole (JIRA)

Deploy just testing artifacts from hibernate-core, not all tests ---------------------------------------------------------------- Key: HHH-5904 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5904 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 Ceate/install/deploy just hibernate-testing.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5907) derby does not support materialize a LOB locator outside the transaction in which it was created

by Strong Liu (JIRA)

derby does not support materialize a LOB locator outside the transaction in which it was created ------------------------------------------------------------------------------------------------- Key: HHH-5907 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5907 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Strong Liu Assignee: Strong Liu Priority: Minor Fix For: 3.6.2, 4.0.0.Alpha1 according to derby's reference guide: {quote} Derby does not materialize a LOB when you use the BLOB or CLOB data type {quote} and this causes org.hibernate.test.lob.BlobLocatorTest fail -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5906) Expose AbstractEntityPersister.getPropertyUniqueness() as public for OGM to use

by Emmanuel Bernard (JIRA)

Expose AbstractEntityPersister.getPropertyUniqueness() as public for OGM to use ------------------------------------------------------------------------------- Key: HHH-5906 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5906 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.6.2, 4.0.0.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2011