March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-661) Improve documentation around query dsl options like ignoreAnalyzer and ignoreFieldBridge

by Hardy Ferentschik (JIRA)

Improve documentation around query dsl options like ignoreAnalyzer and ignoreFieldBridge ---------------------------------------------------------------------------------------- Key: HSEARCH-661 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-661 Project: Hibernate Search Issue Type: Improvement Components: documentation Affects Versions: 3.3.0.Final Reporter: Hardy Ferentschik Fix For: 3.4.0 The _Query Options_ section mentioned that these options exist, but does not explain why they are needed in some cases and what happens per default when _onField(s)()_ is used. See also forum thread - https://forum.hibernate.org/viewtopic.php?f=9&t=1008943 -- 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

15 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-452) Incorrect Paths when using fluent API to add constraints to a context

by Glen Hilton (JIRA)

Incorrect Paths when using fluent API to add constraints to a context --------------------------------------------------------------------- Key: HV-452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-452 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Beta2, 4.2.0.Beta1 Reporter: Glen Hilton The bug actually should be found by existing test cases in ConstraintValidatorContextTest, but there happens to be a bug there too. First to the test case bug: In ConstraintValidatorContextTest, within the testing utility method assertMessageAndPath there's a call to TestUtil.assertEqualPaths. TestUtil.assertEqualPaths doesn't assert anything it returns a boolean, this fact causes line 156: {{assertEqualPaths( messageAndPath.getPath(), PathImpl.createPathFromString( expectedPath ) );}} to not actually test anything. Given this testing bug, we don't know that ConstraintValidatorContextTest.testMultipleMessages line 144: {{assertMessageAndPath( messageAndPathList.get( 1 ), message2, "" );}} should actually fail. As a quick and dirty fix to the test cases, we could wrap the existing line 144 with assertTrue, so it would end up: {{assertTrue(assertMessageAndPath( messageAndPathList.get( 1 ), message2, "" ))}} Now two of the tests in ConstraintValidatorContextTest will fail. These test cases appear to fail because within ConstraintValidatorContextImpl, all of the subclasses (ErrorBuilderImpl, NodeBuilderImpl, InIterableNodeBuilderImpl) are getting instantiated with a reference to the propertyPath at the "base" level (ConstraintValidatorContextImpl.propertyPath). Meaning when the subclasses update the propertyPath they are actually all updating the same underlying object, leading to incorrect paths being created. This bug appears to have been introduced with HV-395 as before there was code to create a copy of the path when ErrorBuilderImpl.addNode was called. Sorry I don't have an actual fix to provide, as I don't fully grasp HV-395. p.s. thanks for all the hard work! -- 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

15 years

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3008) Cascade delete does not work with unidirectional @OneToMany and @JoinTable

by Daniel Dyer (JIRA)

Cascade delete does not work with unidirectional @OneToMany and @JoinTable -------------------------------------------------------------------------- Key: HHH-3008 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3008 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Standalone entity manager (JavaSE 5.0). H2 database. Reporter: Daniel Dyer A unidirectional one-to-many relationship defined as follows: public class Owner { @OneToMany(cascade = CascadeType.ALL) @JoinTable(name = "owner_element", joinColumns = @JoinColumn(name = "owner_id", nullable = false, updatable = false), inverseJoinColumns = @JoinColumn(name = "element_id", nullable = false, updatable = false)) private List<Element> elements; // ... } Attempting to delete an instance of Owner should also delete all associated instances of Element. Instead I get the following error: SEVERE: Referential integrity constraint violation: FK56BBF9C487E817D: PUBLIC.OWNER_ELEMENT FOREIGN KEY(OWNER_ID) REFERENCES PUBLIC.OWNER(ID) [23003-63] This is because Hibernate attempts to delete the Owner row without first removing the rows from the join table. -- 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

15 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5914) Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals

by Gail Badner (JIRA)

Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals ----------------------------------------------------------------------------------- Key: HHH-5914 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5914 Project: Hibernate Core Issue Type: Improvement Components: core, documentation Reporter: Gail Badner Fix For: 4.0.0.Alpha3 Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals. Manuals should refer to constants in org.hibernate.type.StandardBasicTypes instead. -- 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

15 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4722) Proxy initialization should be fail-fast when accidentially initializing from event listeners or interceptor

by Joonas Koivunen (JIRA)

Proxy initialization should be fail-fast when accidentially initializing from event listeners or interceptor ------------------------------------------------------------------------------------------------------------ Key: HHH-4722 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4722 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Hibernate 3.2.2 Reporter: Joonas Koivunen Proxy initialization done in event listeners (at least post-update) with an entity that has a mapped collection seems to result in {code}org.hibernate.AssertionFailure: collection [role-of-collection] was not processed by flush(){code} at flush time. By googling up problems like the above assertion failure seems that other people than me have spent quite a time searching for the origin of this problem; for me it was using a toString() of an uninitialized proxy. -- 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

15 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-447) Create documentation for boolean composition of composing constraints

by Hardy Ferentschik (JIRA)

Create documentation for boolean composition of composing constraints --------------------------------------------------------------------- Key: HV-447 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-447 Project: Hibernate Validator Issue Type: Bug Components: documentation Reporter: Hardy Ferentschik Fix For: 4.2.0.CR1 Seems we forgot the online docs for HV-390 -- 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

15 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-720) Add a screenshot of amazon.com and the related concepts pointed via arrow for faceting

by Emmanuel Bernard (JIRA)

Add a screenshot of amazon.com and the related concepts pointed via arrow for faceting -------------------------------------------------------------------------------------- Key: HSEARCH-720 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-720 Project: Hibernate Search Issue Type: Improvement Components: documentation Affects Versions: 3.4.0.CR1 Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.4.0 -- 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

15 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2989) @Loader using named queries returns null

by Jose Noheda (JIRA)

@Loader using named queries returns null ---------------------------------------- Key: HHH-2989 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2989 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Hibernate Annotations 3.3.0, Hibernate Entity Manager 3.3.1 Reporter: Jose Noheda When using entitymanager.find (class, pk) with a @Loader annotation declared the org.hibernate.persister.entity.NamedQueryLoader load function performs a query.list() call (line 57). This call returns a List of entities and the list is correctly filled with one entry (org.hibernate.impl.SessionImpl line 1121). After returning, the line 62 (of NamedQueryLoader): return session.getPersistenceContext().getEntity( new EntityKey( id, persister, session.getEntityMode() ) ) is unable to find it though. -- 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

15 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-623) Support for faceting search results

by G Fernandes (JIRA)

Support for faceting search results ----------------------------------- Key: HSEARCH-623 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-623 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: G Fernandes I've been asked more than once about the possibility to support facet retrieval from the search results. The idea is to categorize the results of a query into buckets containing a label plus a number of occurrences. Consider an example: I have a Book entity containing a language field. When I search for Books, I'd like to obtain not only a List<Book>, but also a list of languages and how many books from the search results fit into each of these languages, so that I can render the results as: Found 17 Books: English (10) Italian (5) Spanish (2) It'd be also possible to facet on more than a field at the same time, similar to what's being done with projections. Facet calculation would be done at query time reading directly from the index, probably by using a plugable strategy, examples would be LuceneFieldCacheStrategy and TermEnumStrategy. Asking for facets would be done at API level, probably with a decorator on top of QueryBuilder something like facetQueryBuilder.facetOn("field1").facetOn("field2").results().facets(); WDYT? -- 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

15 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-1976) NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc

by Lóránt Pintér (JIRA)

NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc --------------------------------------------------------------------------------------------------------- Key: HHH-1976 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1976 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3, 3.2.0.cr2 Reporter: Lóránt Pintér I have a custom NamingStrategy that overrides classToTableName in EJB3NamingStrategy. Prior to upgrading to Hibernate 3.1.3, my NamingStrategy implementation received the correct classnames as documented in the javadoc at http://www.hibernate.org/hib_docs/v3/api/org/hibernate/cfg/NamingStrategy... Since then, it only receives the name of the class without the package specification. I tried upgrading to 3.2.0.cr2, but it didn't help. -- 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

15 years

9
15
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 March 2011