July 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2708) attribute order-by don't devlared on hibernate-mapping-3.0.dtd

by Sunteya (JIRA)

attribute order-by don't devlared on hibernate-mapping-3.0.dtd -------------------------------------------------------------- Key: HHH-2708 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2708 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Reporter: Sunteya HHH-1414 bug already fixed order-by attribute on the <many-to-many/> element but the dtd file don't allow use order-by attribute. -- 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, 4 months

2
2
0 / 0

[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, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5180) StandardQueryCache.get() does not handle EntityNotFoundException for natural key lookups

by Gail Badner (JIRA)

StandardQueryCache.get() does not handle EntityNotFoundException for natural key lookups ---------------------------------------------------------------------------------------- Key: HHH-5180 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5180 Project: Hibernate Core Issue Type: Bug Components: caching (L2), core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.6 This is the same as HHH-3478, except it's for 3.6. In 3.6 we can use JPA exceptions, so the fix will be different. -- 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, 4 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5393) @MapKey with embeddable value

by Harald Wellmann (JIRA)

@MapKey with embeddable value ----------------------------- Key: HHH-5393 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5393 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.3 Environment: Hibernate 3.5.3, PostgreSQL 8.4.3 Reporter: Harald Wellmann Map<Basic, Embeddable> does not work, when the map key is a persistent field of the value. The map key shall not be represented as a separate table column, this is why the example uses @MapKey and not @MapKeyColumn. Example: {code:java} @Embeddable public class LocalizedString { private String language; private String text; } @Entity public class MultilingualString { @Id private long id; @ElementCollection(fetch=FetchType.EAGER) @MapKey(name = "language") @CollectionTable(schema = "jpa", name = "multilingual_string_map", joinColumns = @JoinColumn(name = "string_id")) private Map<String, LocalizedString> map = new HashMap<String, LocalizedString>(); } {code} Hibernate appears to expect an Entity as map value: org.hibernate.AnnotationException: Associated class not found: LocalizedString Detailed discussion of this use case: http://hwellmann.blogspot.com/2010/07/jpa-20-mapping-map.html -- 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, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HV-355) RangeDef's min() and max() are just wrong

by Trond Valen (JIRA)

RangeDef's min() and max() are just wrong ----------------------------------------- Key: HV-355 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-355 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 4.1.0.Final Environment: Hibernate 3.3.2.GA and Oracle XE 10.2.0 Reporter: Trond Valen Assignee: Hardy Ferentschik public RangeDef min(long min) { addParameter( "value", min ); return this; } public RangeDef max(long max) { addParameter( "value", max ); return this; } Do I need a test case for this? Shouldn't these methods run addParameter("min", min) and addParameter("max", max)? I got an exception with "Unknown parameters"... I made a MyRangeDef where I fixed this, and it was all good :) -- 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, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5426) HQL update/delete does not invalidate the query cache

by Emond Papegaaij (JIRA)

HQL update/delete does not invalidate the query cache ----------------------------------------------------- Key: HHH-5426 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5426 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.4 Reporter: Emond Papegaaij Attachments: QueryCacheTest.java Update/delete queries performed via HQL do not invalidate the query cache. For example, a 'delete from Item' does not invalidate a 'select count(*) from Item' query performed earlier. The attached test case can be added to QueryCacheTest (in the testsuite) to demonstrate the problem. -- 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-4627) Configurable Query Plan Cache

by Frank Daspro (JIRA)

Configurable Query Plan Cache ----------------------------- Key: HHH-4627 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4627 Project: Hibernate Core Issue Type: New Feature Components: query-hql Affects Versions: 3.2.2 Environment: Hibernate 3.22 GA, Oracle 10G database Reporter: Frank Daspro Our application heavily uses dynamic sql some of which are highly parameterised and with many permutations. Out of neccessity we also have a very large JVM heap space (12GB). As a result we end up with a very large memory utilisation for the Query Plan cache. From a recent memory dump it was noted the QueryPlanCache had 25000 entries and consuming 2.5GB of heap space. Our full Garbage collections end up taking longer than it would normally take with a smaller QueryPlanCache. I understand via a related issue (http://opensource.atlassian.com/projects/hibernate/browse/HHH-3191) there is a hard limit of 128 entries, and an endless soft limit which is only garbage collected during a full garbage collection. It would be nice if the following features could be added: 1) Configuration options to specify the hard and soft limits (with a 0 to disable or similar). 2) Configurable at the query level such that specific queries can be excluded from the the QueryPlanCache. eg. something like hibernateQuery.setParsedHQLCacheable(false). -- 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
1
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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2010