November 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-4) Document how to use the processor in different environments

by Hardy Ferentschik (JIRA)

Document how to use the processor in different environments ----------------------------------------------------------- Key: METAGEN-4 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-4 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Include the documentation into the project (docbook?!) and blog about it. -- 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 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3841) Add support for lock timeouts

by Christian Daszenies (JIRA)

Add support for lock timeouts ------------------------------ Key: HHH-3841 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3841 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Christian Daszenies It would be nice to support (pessimistic) lock timeouts, as with Oracle's SELECT ... FOR UPDATE WAIT [seconds] syntax. There has been an issue in Project hibernate2 (HB-950) with the same request. -- 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 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-87) Avoid to trigger optimization during intermediate batches

by Emmanuel Bernard (JIRA)

Avoid to trigger optimization during intermediate batches --------------------------------------------------------- Key: HSEARCH-87 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-87 Project: Hibernate Search Issue Type: New Feature Reporter: Emmanuel Bernard A queue can be batched (esp session.index()) optimization should be delayed for the end of the transaction -- 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 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3125) BigDecimal support for id generator from DB sequence

by Tomas Rada (JIRA)

BigDecimal support for id generator from DB sequence ---------------------------------------------------- Key: HHH-3125 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3125 Project: Hibernate3 Issue Type: New Feature Environment: Hibernate 3.2, Oracle 10 Reporter: Tomas Rada Currently with using BigDecimal as entity id is thrown exception " this id generator generates long, integer, short or string" - class "IdentifierGeneratorFactory". Is there possibility to add BigDecimal support for id generator? -- 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 months

6
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3968) Error in SchemaUpdate using HSQLDialect with BigInteger or BigDecimal primary keys [similar to HHH.3323]

by Jonathan Mastin (JIRA)

Error in SchemaUpdate using HSQLDialect with BigInteger or BigDecimal primary keys [similar to HHH.3323] -------------------------------------------------------------------------------------------------------- Key: HHH-3968 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3968 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.SP1 Environment: HSQLDB: 1.8.0.9 Reporter: Jonathan Mastin Problem --------------- When using HSQLDialect, the following code fails during schema creation: @Entity public class Test { @Id @GeneratedValue(strategy = GenerationType.AUTO) private BigInteger id; } Log output: ---------------- ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create table Test (id numeric generated by default as identity (start with 1), primary key (id)) ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - Wrong data type: id in statement [create table Test (id numeric generated by default as identity (start with 1)] Expected --------------------------------- The column type is being set as "numeric", but it needs to be set as "integer" or "bigint" for HSQL to be able to parse. >From the HSQL manual: "The supported form is(<colname> INTEGER GENERATED BY DEFAULT AS IDENTITY(START WITH n, [INCREMENT BY m])PRIMARY KEY, ...). Support has also been added for BIGINT identity columns. As a result, an IDENTITY column is simply an INTEGER or BIGINT column ..." -- 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 months

2
1
0 / 0

[Hibernate-JIRA] Created: (METAGEN-9) Implement mixed configuration (annotation + xml)

by Hardy Ferentschik (JIRA)

Implement mixed configuration (annotation + xml) ------------------------------------------------ Key: METAGEN-9 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-9 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik At the moment only xml or annotations are considered. Configurations have to be "merged" -- 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 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4578) Criteria is missing read-only flag

by Ales Justin (JIRA)

Criteria is missing read-only flag ---------------------------------- Key: HHH-4578 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4578 Project: Hibernate Core Issue Type: Improvement Components: query-criteria Affects Versions: 3.5.0-Beta-2 Reporter: Ales Justin Attachments: readOnly.patch Query API has a notion of read-only, whereas Criteria doesn't. * https://forum.hibernate.org/viewtopic.php?p=2353610&sid=98ea30c01ac78df6a... Is this intentional or oversight? -- 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 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2975) Interceptor onFlushDirty collections - previous and current state the same instance

by Clayton J. Kovar (JIRA)

Interceptor onFlushDirty collections - previous and current state the same instance ----------------------------------------------------------------------------------- Key: HHH-2975 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2975 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Hibernate 3.2.2 - Oracle thin driver 10.1.0.4.0 Reporter: Clayton J. Kovar When calling Session.merge(entity) {therefore the previous state is available} the interceptor's onFlushDirty is called and the previous state for all of the simple properties correctly passes the previous values but with a collection the same collection instance is passed in both the previous and current state arrays. So far I have only seen this behavior on a Map with a one-to-many relationship to another entity. I have not tried it yet with Lists, Sets, or Bags. I'm assuming this is not expected behavior, but please let me know if it is. Best regards. -- 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 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2862) Collection is not associated with any session exception when doing an eager fetch on a non-unique collection.

by Paul Andrews (JIRA)

Collection is not associated with any session exception when doing an eager fetch on a non-unique collection. ------------------------------------------------------------------------------------------------------------- Key: HHH-2862 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2862 Project: Hibernate3 Issue Type: Bug Environment: Hibernate 3.1.3 - Hibernate 3.2.5, HSQLDB, Java5 Reporter: Paul Andrews It is basically caused by having an eager collection where the key of the collection is not unique in the results. The code works as follows in CollectionType.getCollection(): .... persistenceContext.addUninitializedCollection( persister, collection, key ); // some collections are not lazy: if ( initializeImmediately( entityMode ) ) { session.initializeCollection( collection, false ); } else if ( !persister.isLazy() ) { persistenceContext.addNonLazyCollection( collection ); } if ( hasHolder( entityMode ) ) { session.getPersistenceContext().addCollectionHolder( collection ); } if persistenceContext.addUninitializedCollection() detects that the collection with the given key has already been added it clears the session on the old instance of the collection (sets it to null). However, that collection has already been added to the persistence context by an earlier call to this method. So later when StatefulPersistenceContext.initializeNonLazyCollections() is called it iterates through all of the collections in the persistence context (including those which have had their session set to null by addUninitializedCollection()), calling forceInitialization() which throws a 'collection is not associated with any session' 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

16 years, 2 months

10
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3695) RegionFactory's no-arg constructor does not get invoked

by Paul Cowan (JIRA)

RegionFactory's no-arg constructor does not get invoked ------------------------------------------------------- Key: HHH-3695 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3695 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.3.1 Reporter: Paul Cowan Priority: Trivial RegionFactory's class Javadoc says: * Implementors should define a constructor in one of two forms:<ul> * <li>MyRegionFactoryImpl({@link java.util.Properties})</li> * <li>MyRegionFactoryImpl()</li> * </ul> but SettingsFactory.createRegionFactory only looks for the one that takes a Properties class. This is relatively minor, I don't think 'fixing' this by just correcting the javadoc is really that big a deal but have patches for both ways. -- 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 months

2
3
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 November 2009