January 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6809) FooBarTest.testFindByCriteria() fails on SQL Server due to mixed expectations for Criteria.setMaxResults(0)

by John Verhaeg (JIRA)

FooBarTest.testFindByCriteria() fails on SQL Server due to mixed expectations for Criteria.setMaxResults(0) ----------------------------------------------------------------------------------------------------------- Key: HHH-6809 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6809 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR5 Environment: MS SQL Server Reporter: John Verhaeg Fix For: 4.0.0.next Looks like some dialects treat 0 as meaning no limit and others as literally zero rows. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-6953) Envers: ManyToOne association returns null for audited entities when insertable/updatable=false

by Steffen Ryll (JIRA)

Envers: ManyToOne association returns null for audited entities when insertable/updatable=false ----------------------------------------------------------------------------------------------- Key: HHH-6953 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6953 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.6.9, 4.0.0.Final Environment: Hibernate Core/Envers 3.6.9 and 4.0.0.Final, HSQLDB 2.2 Reporter: Steffen Ryll Attachments: envers-one2many-insertupdatefalse-bug_20120109.zip We found a problem retrieving historical revisions of entities when there is a OneToMany association involved. Going from the one side to the many side always returns null. However, if I load that association through the normal entity manager, it is non-null (correctly). I have created a tiny test case (see attachment) that demonstrates the effect. The special twist is that removing the (insertable=false, updatable=false) parameters to the @JoinColumn annotation in Piece.java makes it work. But we do need those two options in our real project and removing them is no option. I will start looking into the Envers code and try tracking down the reason for that NullPointerException, but wanted to have a bug report created in the first place. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6885) Replace ClassLoaderAwareCache with AdvancedCache.with(ClassLoader)

by Sanne Grinovero (JIRA)

Replace ClassLoaderAwareCache with AdvancedCache.with(ClassLoader) ------------------------------------------------------------------ Key: HHH-6885 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6885 Project: Hibernate Core Issue Type: Task Reporter: Sanne Grinovero Fix For: 4.0.0.next Infinispan 5.1 introduces AdvancedCache.with(ClassLoader) , which is a cleaner approach to the previously used ClassLoaderAwareCache -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
9
0 / 0

[Hibernate-JIRA] Commented: (HHH-1152) Value object(<component>) inheritance mapping

by Mircea D. (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1152?page=c... ] Mircea D. commented on HHH-1152: -------------------------------- I agree with things being said here. I also need this dearly! See http://blog.xebia.com/2007/09/25/hibernate-component-value-object-inherit... for a motivation. > Value object(<component>) inheritance mapping > --------------------------------------------- > > Key: HHH-1152 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1152 > Project: Hibernate Core > Issue Type: New Feature > Components: core > Affects Versions: 3.1 beta 2 > Reporter: Vjeran Marcinko > Priority: Minor > > Though fine-grained object mapping is one of Hibernate's main objectives, it still doesn't support *value object* (<component>) inheritance mapping, only entity inheritance mapping. > It would be best if <component> tag could also contain similar tags for inheritance as entity does. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6951) JPA IdentifiableType.geIdType() does not return annotated @IdClass type

by Oliver Gierke (JIRA)

JPA IdentifiableType.geIdType() does not return annotated @IdClass type ----------------------------------------------------------------------- Key: HHH-6951 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6951 Project: Hibernate Core Issue Type: Bug Components: metamodel Affects Versions: 3.6.9, 4.0.0.Final Reporter: Oliver Gierke {{AbstractIdentifiableType}} only returns an id type for {{getIdType()}} if the id is a simple one, which means it's a single {{@Id}} or {{@EmbeddableId}} annotated attribute. If you use {{@IdClass}} with an entity, the according metadata object throws an exception. It should return the value of the {{@IdClass}} annotation instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6948) An error happed in a JavaEE applicaiton which using Hibernate 3.1.3 occur ON Dec 28, 2011. In a call of merge, a field of

by xiaombing2011 (JIRA)

An error happed in a JavaEE applicaiton which using Hibernate 3.1.3 occur ON Dec 28, 2011. In a call of merge, a field of ------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6948 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6948 Project: Hibernate Core Issue Type: Bug Reporter: xiaombing2011 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6812) HQL query for map value leads to incorrect joins in SQL

by Neukomm (JIRA)

HQL query for map value leads to incorrect joins in SQL ------------------------------------------------------- Key: HHH-6812 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6812 Project: Hibernate Core Issue Type: Bug Components: query-hql, query-sql Affects Versions: 3.6.7 Environment: Oracle Java 1.6.0_29, Hibernate 3.6.7-Final, Hsqldb 2.2.5 Reporter: Neukomm Attachments: map_query_test.zip Whenever an expression like 'where p.map['key'] = :val' is used in HQL, the join between the entity table and the map value table is not done correctly. This leads to missing results. The attached test case uses HQL like this: from MapQueryEntity p where p.name = 'B' or p.map['key'] = 'value' the corresponding sql looks like this: select mapqueryen0_.id as id0_, mapqueryen0_.name as name0_ from MapQueryEntity mapqueryen0_ cross join MapQueryEntity_map map1_ where mapqueryen0_.id=map1_.ident and map1_.mkey = 'key' and ( mapqueryen0_.name='B' or map1_.mvalue='value' ) This leads to all entities that don't have a map entry for key 'key' not to be in the result, even if they have name 'B'. SQL that would return the correct rows (at least on hsqldb) could e.g. look like this: select mapqueryen0_.id as id0_, mapqueryen0_.name as name0_ from MapQueryEntity mapqueryen0_ left outer join MapQueryEntity_map map1_ on mapqueryen0_.id=map1_.ident where mapqueryen0_.name='B' or (map1_.mkey = 'key' and map1_.mvalue='value') Looks like org.hibernate.hql.ast.tree.IndexNode (which seems to be responsible for the hql/sql translation if '[]' is used) doesn't work correctly for this case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6942) Envers Collection revision entries don't include deletes on detached entity saveOrUpdate

by Karl Walsh (JIRA)

Envers Collection revision entries don't include deletes on detached entity saveOrUpdate ---------------------------------------------------------------------------------------- Key: HHH-6942 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6942 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.6.8 Reporter: Karl Walsh Attachments: TestCase.zip Please see http://community.jboss.org/thread/175787?tstart=0 When a detached entity has some children removed by replacing the collection of children with a smaller collection, the audit entries do not contain the deletes when performing a saveOrUpdate. Using merge does include the correct delete revisions. e.g Parent contains children Child(A) and Child(B) Parent -> (ChildA, ChildB) If this collection is replaced with a new collection: Parent -> (ChildA) And a saveOrUpdate is issued on the parent, the audit entries doesn't include the delete for ChildB. However, if the child is explicitly removed from the collection: Parent.getChildren().remove(ChildB) The saveOrUpdate works as expected and the delete of ChildB is audited correctly. Using merge instead of saveOrUpdate allows the collection of children to be replaced rather than an explicit removal, and audit entries correctly register the delete of ChildB. I have not tested this beyond 3.6.8.Final. I have attached a spring/maven test case. Any questions let me know. Karl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1031) Typos in the "Boosting" section of the documentation

by Guillaume Smet (JIRA)

Typos in the "Boosting" section of the documentation ---------------------------------------------------- Key: HSEARCH-1031 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1031 Project: Hibernate Search Issue Type: Patch Components: documentation Affects Versions: 4.0.0.Final Reporter: Guillaume Smet Priority: Trivial Hi, I spotted a couple of typos in the "Boosting" section of the documentation: pull request to follow. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-546) LazyValidatorFactory does not allow alternative bean validation providers

by Hardy Ferentschik (JIRA)

LazyValidatorFactory does not allow alternative bean validation providers ------------------------------------------------------------------------- Key: HV-546 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-546 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Final Reporter: Hardy Ferentschik Fix For: 4.3.0.next The current implementation of _LazyValidatorFactory_ does not allow alternative validation providers. The idea of the class is to make sure that Hibernate Validator is the default (it should be the first returned), but it should also allow for custom providers. For this to work logic as in _Validation#DefaultValidationProviderResolver_ is needed. The same problem applies to _org.jboss.as.ee.beanvalidation.LazyValidatorFactory_ and _org.jboss.as.jpa.validator.JPALazyValidatorFactory_. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2012