July 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-719) Upload Hibernate-Annotations 3.3.1.GA to central maven repository

by Andreas Schildbach (JIRA)

Upload Hibernate-Annotations 3.3.1.GA to central maven repository ----------------------------------------------------------------- Key: ANN-719 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-719 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.3.1.GA Reporter: Andreas Schildbach Could you upload Hibernate-Annotations 3.3.1.GA to the central maven repository? Would you also add the sources? -- 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, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2980) Error "org.hibernate.HibernateException: cannot simultaneously fetch multiple bags" not specific enough

by Dobes Vandermeer (JIRA)

Error "org.hibernate.HibernateException: cannot simultaneously fetch multiple bags" not specific enough ------------------------------------------------------------------------------------------------------- Key: HHH-2980 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2980 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.2.5 Reporter: Dobes Vandermeer When I get this exception: org.hibernate.HibernateException: cannot simultaneously fetch multiple bags I don't know what to do except google. Why not spruce it up a little to say something like: For class X, multiple collection fields are marked for eager fetching: a, b, c; this is not supported by Hibernate in releases after 3.2.x -- 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, 5 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3191) QueryPlanCache cache size

by Julien Kirch (JIRA)

QueryPlanCache cache size ------------------------- Key: HHH-3191 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3191 Project: Hibernate3 Issue Type: Improvement Components: query-hql Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, all platform Reporter: Julien Kirch On a large application with many (currently 696) named queries in hbm files we have a performance issue with the QueryPlanCache cache size: The SoftLimitMRUCache used in the QueryPlanCache use 128 hard references, the other being soft references, and this number is hardcoded. As we have much more querries in the application, we spend much time in recompiling the same queries when they are evicted from the cache. As the QueryPlanCache has a SessionFactoryImplementor as parameter, adding a new parameter to define the query cache plan size would be trivial; what's your opinion about this ? -- 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, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2431) QueryPlanCache grows without bound. Eventually gets OutOfMemoryException

by Eric Goff (JIRA)

QueryPlanCache grows without bound. Eventually gets OutOfMemoryException -------------------------------------------------------------------------- Key: HHH-2431 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2431 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: all versions, all platforms Reporter: Eric Goff Every time you execute a query, and that query does not match any existing queries in the QueryPlanCache, that query is *always* added to the Query Plan Cache, along with a lot of various antlr stuff. There seems to be no way to control it. Minimally, there should be some sort of heap of query plans where the least used query plan is ejected when the cache reaches it max size. The cache size should, of course, be user configurable. -- 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, 5 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HBX-1000) Problem with PostgreSQL using uppercase letters in tables

by Ruediger Engelberger (JIRA)

Problem with PostgreSQL using uppercase letters in tables --------------------------------------------------------- Key: HBX-1000 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1000 Project: Hibernate Tools Issue Type: Bug Components: reverse-engineer Affects Versions: 3.2.beta11 Environment: Hibernate 3.2.5.ga, Hibernate Tools 3.2.0 beta9a, PostgreSql 8.2, postgresql-8.2-506.jdbc3.jar, Eclipse 3.3.0, all running on Windows XP at the moment (including PostgreSql) Reporter: Ruediger Engelberger I have problems using Hibernate tools when using upper case letters in a PostgreSQL database. I can configure Hibernate Tools for my local PostgreSql installation without any problems. I can access the table structure in the view Hibernate Configurations and do reverse engineering by creating XML mappings and beans. No problem. But when I'm using upper case characters in table names Hibernate Tools can't access the table structures any more. Hibernate Configuration shows the tables, but when I want to see the columns, it doesn't show anything. Reverse engineering also doesn't work any more. So, the following works: TABLE cms_clusterMessage pk_clustermessageid fk_clusternodeid messagetype messagedetail The following doesn't work: TABLE cms_clusterMessage PK_ClusterMessageId FK_ClusterNodeId MessageType MessageDetail I tried to use different JDBC drivers because I thought it could be a bug of the driver. But it wasn't. -- 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, 5 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2510) override equals()/hashCode() in AliasToBeanResultTransformer

by Maxim Gordienko (JIRA)

override equals()/hashCode() in AliasToBeanResultTransformer ------------------------------------------------------------ Key: HHH-2510 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2510 Project: Hibernate3 Type: Improvement Versions: 3.2.2 Reporter: Maxim Gordienko AliasToBeanResultTransformer whould override equals()/hashCode() to allow convenient second level query caching. Now the only way is to maintain single transformer instance per bean class to allow query cache hit. -- 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, 5 months

3
9
0 / 0

[Hibernate-JIRA] Created: (ANN-663) @JoinColumn must be set for @AssociationOverride to work

by Bas van den Berg (JIRA)

@JoinColumn must be set for @AssociationOverride to work -------------------------------------------------------- Key: ANN-663 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-663 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate 3.2 , MySQL Reporter: Bas van den Berg Priority: Minor The following error is given when overiding the joincolumn which has not been set explicitly: Illegal attempt to define a @JoinColumn with a mappedBy association see http://forum.hibernate.org/viewtopic.php?t=960621&highlight= -- 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, 5 months

4
7
0 / 0

[Hibernate-JIRA] Created: (ANN-604) There is no annotation to specify default value for a column

by Nicolae Bucalaete (JIRA)

There is no annotation to specify default value for a column ------------------------------------------------------------ Key: ANN-604 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-604 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Nicolae Bucalaete Priority: Critical In hibernate annotation you can't specify default value for a column. If you use xml files for mapping then you have this feature. I consider that this is a major problem with annotation. -- 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, 5 months

15
17
0 / 0

[Hibernate-JIRA] Created: (HHH-3231) org.hibernate.id.enhanced.TableGenerator throws "IllegalArgumentException: alias not found: tbl" under Oracle

by Király Attila (JIRA)

org.hibernate.id.enhanced.TableGenerator throws "IllegalArgumentException: alias not found: tbl" under Oracle ------------------------------------------------------------------------------------------------------------- Key: HHH-3231 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3231 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6GA, Oracle 10g Reporter: Király Attila Attachments: hibernate_etg_ora.zip org.hibernate.id.enhanced.TableGenerator always throws the following exception if I want to save a new object to Oracle: java.lang.IllegalArgumentException: alias not found: tbl at org.hibernate.sql.ForUpdateFragment.<init>(ForUpdateFragment.java:36) at org.hibernate.dialect.Dialect.applyLocksToSql(Dialect.java:970) at org.hibernate.id.enhanced.TableGenerator.configure(TableGenerator.java:194) at org.hibernate.id.IdentifierGeneratorFactory.create(IdentifierGeneratorFactory.java:104) I attach an example to this case. The example is loosely based on the tutorial example, that comes with Hibernate. It contains a Person object that is saved to db using the enhanced.TableGenerator as id generator. To keep the zip small only the jars of jdbc driver are included, the jars needed from hibernate distribution are listed in lib/readme.txt. The zip also contains a modified TableGenerator that works with Oracle. This version was made by forum user stomp and more information about it can be read here: http://forum.hibernate.org/viewtopic.php?t=980933 It changes the 194th row of TableGenerator from this.query = dialect.applyLocksToSql( query, lockMap, CollectionHelper.EMPTY_MAP ); to this.query = dialect.applyLocksToSql( query, lockMap, Collections.singletonMap("tbl", new String[] {valueColumnName}) ); -- 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, 5 months

5
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2350) 2nd level cache broken for inverse bidirectional one-to-many relation

by Burkhard Graves (JIRA)

2nd level cache broken for inverse bidirectional one-to-many relation --------------------------------------------------------------------- Key: HHH-2350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2350 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Database: MySQL, HSQL, ... (seems not to be important) Reporter: Burkhard Graves Attachments: testcase.tgz When using "inverse" one-to-many relations as described in "2.4.6.2.3. Bidirectional association with indexed collections" (http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.ht...) hibernate is wrong when activating 2nd level cache. See the attached example (unzip in /usr/local/hibernate-annotations-3.2.1.GA, testname=org.hibernate.test.annotations.invonetomany.InverseOneToManyTest). More details can be found here: http://forum.hibernate.org/viewtopic.php?t=969456 (and also in InverseOneToManyTest.java). -- 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, 5 months

3
12
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2008