June 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (OGM-133) Expose table, column names and column values from EntityKey and RowKey

by Emmanuel Bernard (JIRA)

Expose table, column names and column values from EntityKey and RowKey ---------------------------------------------------------------------- Key: OGM-133 URL: https://hibernate.onjira.com/browse/OGM-133 Project: Hibernate OGM Issue Type: Improvement Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2666) subselect fetching ignores max results

by James Roper (JIRA)

subselect fetching ignores max results -------------------------------------- Key: HHH-2666 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2666 Project: Hibernate3 Issue Type: Improvement Components: query-hql, query-sql Affects Versions: 3.2.1 Environment: Hibernate 3.2.1 HSQLDB 8.0 Reporter: James Roper Priority: Minor When maxResults is set for a query, the hibernate subselect fetching strategy ignores it. For example, I have a class entry, that has a list of comments, which are configured to use the subselect fetching strategy. You can see that in the original query, only the top ? results are fetched: select top ? entry0_.id as id0_, entry0_.title as title0_, entry0_.entry as entry0_, entry0_.time as time0_, entry0_.category_id as category5_0_ from Entry entry0_ order by entry0_.time desc But then when it does the sub select query to lazily load the comments, this is the query it runs: select comments0_.entry_id as entry5_1_, comments0_.id as id1_, comments0_.id as id1_0_, comments0_.time as time1_0_, comments0_.comment as comment1_0_, comments0_.author as author1_0_ from Comment comments0_ where comments0_.entry_id in ( select entry0_.id from Entry entry0_ ) order by comments0_.time desc So, it loads every single comment in the database, even though only the comments for the top ? entries are needed. Of course, if there was no order by clause on the first query, the sub select may not return the same results, so it should probably only do this when there is an order by clause in the first query, and it should make sure it includes the order by clause in the sub select. -- 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

13 years, 9 months

6
12
0 / 0

[Hibernate-JIRA] Created: (ANN-609) Need a way to specify "unsaved-value" strategy using annotations

by Suji Suresh (JIRA)

Need a way to specify "unsaved-value" strategy using annotations ---------------------------------------------------------------- Key: ANN-609 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-609 Project: Hibernate Annotations Issue Type: Bug Environment: Hibernate 3.2.2, Hibernate-annotations 3.2.1 Reporter: Suji Suresh Hibernate has two ways of specifying a value for primary key: 1. Assign a value before handing it over to Hibernate 2. Have Hibernate generate the value before persisting In my project I have objects of both of the above specified types. In other words I assign value for the primary key for some the objects (lets call these objects "assigned") and for others I have Hibernate generate the value before persisting (lets call these objects "generated"). Since Hibernate annotations does not support "unsaved-value", I do not have a way of specifying "unsaved-value" strategy. While my "generated" objects work perfectly with Hibernate's default "unsaved-value" strategy, I see wrong (but expected) behaviour when I try to persist an "assigned" object that is already present in the database in that, I get StaleStateException instead of DataIntegrityViolationException -- 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

13 years, 9 months

6
9
0 / 0

[Hibernate-JIRA] Created: (HV-582) Introduce a class loading service

by Hardy Ferentschik (JIRA)

Introduce a class loading service --------------------------------- Key: HV-582 URL: https://hibernate.onjira.com/browse/HV-582 Project: Hibernate Validator Issue Type: New Feature Components: engine Affects Versions: 4.3.0.CR1 Reporter: Hardy Ferentschik Fix For: 5.x Currently all class loading in HV happens vi the _LoadClass_ _PrivilegedAction_. In the implementation we first check the thread context class loader and then the current class loader (unless we are loading own package classes in which case we use the current class loader). Historically that was a good approach, but in order to allow for customization in all sorts of environments it makes sense to have a way to configure the class loading approach. This could be done via a _ClassLoaderService_ which can for example be set via the _Configuration_. Depending on which way Bean Validation goes this could be a HV specific feature or something defined by the spec. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] (OGM-196) Update JBoss Logging to 3.1.1.GA

by Sanne Grinovero (JIRA)

13 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-588) Create a marker annotation for entities which should be excluded for validation

by Hardy Ferentschik (JIRA)

Create a marker annotation for entities which should be excluded for validation ------------------------------------------------------------------------------- Key: HV-588 URL: https://hibernate.onjira.com/browse/HV-588 Project: Hibernate Validator Issue Type: New Feature Components: engine Reporter: Hardy Ferentschik Fix For: 5.x We could offer a marker annotation for entities (and maybe package level) to mark entities which should be excluded from validation (eg don't have any constraints). This can reduce metadata processing time and it can also reduce the memory consumption (even if an entity does not contain constraints it will be in the metadata cache). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HV-556) Make AggregateResourceBundleLocator an interface to be included into the public api of HV

by Hardy Ferentschik (JIRA)

Make AggregateResourceBundleLocator an interface to be included into the public api of HV ----------------------------------------------------------------------------------------- Key: HV-556 URL: https://hibernate.onjira.com/browse/HV-556 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.2.0.Final Reporter: Hardy Ferentschik Fix For: 5.x Currently _AggregateResourceBundleLocator_ is a class, but as part of the spi/public/internal split it should become an interface which is part of the public api. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HV-541) The hibernate-validator-tck-runner project should not be deployed to the maven repository

by Kevin Pollet (JIRA)

The hibernate-validator-tck-runner project should not be deployed to the maven repository ----------------------------------------------------------------------------------------- Key: HV-541 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-541 Project: Hibernate Validator Issue Type: Task Components: build, tck-runner Reporter: Kevin Pollet Fix For: 5.x -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HV-587) stack overflow when having @Valid on cycle

by Michael G (JIRA)

stack overflow when having @Valid on cycle ------------------------------------------ Key: HV-587 URL: https://hibernate.onjira.com/browse/HV-587 Project: Hibernate Validator Issue Type: Bug Reporter: Michael G When I have some entities referencing each other (a cycle), the annotation @Valid is on the corresponding getters and there is not really something to be validated on these entities (no @NotNull, ... is present) I end up in a recursion which leads to a stack overflow. If there are some @NotNull the detection of cycles does work fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HV-571) Align method level validation w/ Bean Validation 1.1

by Hardy Ferentschik (JIRA)

Align method level validation w/ Bean Validation 1.1 ---------------------------------------------------- Key: HV-571 URL: https://hibernate.onjira.com/browse/HV-571 Project: Hibernate Validator Issue Type: Task Components: engine Reporter: Hardy Ferentschik Fix For: 5.x Currently HV offers method level validation via the _MethodValidator_ interface. This has to be aligned with BV 1.1 where the method level validation calls are part of _Validator_. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
6
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 June 2012