September 2010 - hibernate-issues

[Hibernate-JIRA] Created: (HV-346) Improve some of the default debug/info messages

by Hardy Ferentschik (JIRA)

Improve some of the default debug/info messages ----------------------------------------------- Key: HV-346 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-346 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.1.0.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.2.0 some of the default messages should be more verbose/descriptive. {noformat} util.Version Hibernate Validator 4.0.2.GA engine.ResourceBundleMessageInterpolator ValidationMessages not found. Delegating to org.hibernate.validator.ValidationMessages resolver.DefaultTraversableResolver Found javax.persistence.PersistenceUtil on classpath. resolver.DefaultTraversableResolver Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver. xml.ValidationXmlParser No META-INF/validation.xml found. Using annotation based configuration only {noformat} -- 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, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2007) Hibernate doesn't support optional one-to-one associations

by Andrei Iltchenko (JIRA)

Hibernate doesn't support optional one-to-one associations ---------------------------------------------------------- Key: HHH-2007 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2007 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Reporter: Andrei Iltchenko Hibernate doesn't properly support optional one-to-one associations, e.g. Person (0..1) -- (0..1) Passport. The Hibernate books and reference all talk of two ways of mapping one-to-one associations: 1. using a many-to-one fk association with a unique constraint on the fk; 2. using a pk association. the trouble with both of them is that they enforce the mandatory property of an association end, which sometimes is not desirable. The first way enforces the mandatory property with the uniqueness constraint on the fk, the other by using the fact that one table's pk is its fk. I tried to see if I could adapt the 1st way of representing one-to-ones to support optional association ends. What I did was simply remove the unique and not null constrains from DDL generated (without removing it it would be impossible to have a Person record that doesn't reference a Passport record): from CREATE TABLE Person ( PassUniqueId VARCHAR (32) NOT NULL, version INTEGER NOT NULL, uniqueId VARCHAR (32) NOT NULL, name VARCHAR (40) NULL, PRIMARY KEY (uniqueId), UNIQUE(PassUniqueId), FOREIGN KEY (PassUniqueId) REFERENCES Passport (uniqueId) ); to CREATE TABLE Person ( PassUniqueId VARCHAR (32) NULL, version INTEGER NOT NULL, uniqueId VARCHAR (32) NOT NULL, name VARCHAR (40) NULL, PRIMARY KEY (uniqueId), FOREIGN KEY (PassUniqueId) REFERENCES Passport (uniqueId) ); but leave the uniqueness attribute in the mapping file: <many-to-one name="pass" class="application.business.logic.Passport" cascade="save-update,merge" unique="true" > <column name="PassUniqueId"/> </many-to-one> The resulting solution worked fine and I was able to create instances of Person not linked to a Passport. However Hibernate didn't succed in keeping the association from degrading into a many-to-one. It enabled me to create two Persons linked with the same Passport: PASSUNIQUEID | VIRSION | UNIQUEID | Name ================================================ 0d8b3919fffff | 1 | 0d5fb1dcfff | John 0d8b3919fffff | 0 | 10fd07bdfff | Sam A subsequent attempt at retrieving such Persons with Hibernate failed: org.hibernate.HibernateException: More than one row with the given identifier was found: 0d8b3919ffffffd60151e135b6da0164, for class: application.business.logic.Passport. Hibernate should be able to impose the single end property of such associations without relying on the underlying RDBMS engine and never allow them to degrade to many-to-ones. -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-24) Improve the default message of InvalidStateException

by Mike Quilleash (JIRA)

Improve the default message of InvalidStateException ---------------------------------------------------- Key: HV-24 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-24 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 3.0.0.ga Environment: Any Reporter: Mike Quilleash Doing a printStackTrace on InvalidStateException does not give the actual invalid values anywhere. Would greatly improving debugging speed if this was included by default as often this indicates a programming error. Currently I have to run the code again and debug the right place to find out what the InvalidValues are. -- 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, 6 months

7
14
0 / 0

[Hibernate-JIRA] Created: (HHH-4618) Support pagination: total rows ignore limit

by Dave (JIRA)

Support pagination: total rows ignore limit ------------------------------------------- Key: HHH-4618 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4618 Project: Hibernate Core Issue Type: New Feature Components: core Environment: JBoss 5.1.0GA Reporter: Dave Limit is used for pagination, but total number of rows must be known to calculate page count. Currently we have to use two queries: 1. select * from Student where age<30 limit 20; 2. select count(*) from Student where age<30; For complex query with joins/huge tables, it can be a performance issue. For Criteria API query with group by, there is no way to get row count, for example criteria.setProjection(Projection.projectionList().add(Projections.groupProperty("name")).add(Projections.sum(score))); Currently there is no way to get row count of this query using Criteria API. For MYSQL, SQL_CALC_FOUND_ROWS and FOUND_ROWS() are used to get row count ignoring limit. Pagination is used for all web application. Hibernate should support it in HQL and Criteria API. -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-556) throw meaningfull error on Search static helper methods used with null argument

by Sanne Grinovero (JIRA)

throw meaningfull error on Search static helper methods used with null argument ------------------------------------------------------------------------------- Key: HSEARCH-556 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-556 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Sanne Grinovero Priority: Trivial Fix For: 3.3.0 protect the parameters passed to Search.getFullTextEntityManager, the old createFullTextEntityManager and the jpa versions from being used with null parameter. -- 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, 6 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-600) Sync Search with 3.6.0.Final

by Hardy Ferentschik (JIRA)

Sync Search with 3.6.0.Final ---------------------------- Key: HSEARCH-600 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-600 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.3.0.Beta1 Reporter: Hardy Ferentschik Fix For: 3.3.0.Beta2 Note, we cannot sync with CR2 at the moment due to {code} FullTextSessionImpl.java:[94,7] org.hibernate.search.impl.FullTextSessionImpl is not abstract and does not override abstract method wasInsertedDuringTransaction(org.hibernate.persister.entity.EntityPersister,java.io.Serializable) in org.hibernate.engine.SessionImplementor {code} -- 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, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-449) Consider LUCENE-1575 carefully: not scoring by default?

by Sanne Grinovero (JIRA)

Consider LUCENE-1575 carefully: not scoring by default? ------------------------------------------------------- Key: HSEARCH-449 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-449 Project: Hibernate Search Issue Type: Sub-task Reporter: Sanne Grinovero -- 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, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (METAGEN-37) MappedSuperclass with type parameters result in uncompilable metamodels

by Clint Popetz (JIRA)

MappedSuperclass with type parameters result in uncompilable metamodels ----------------------------------------------------------------------- Key: METAGEN-37 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-37 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.1.0 Reporter: Clint Popetz Assignee: Hardy Ferentschik Attachments: templatebug.tar.gz The attached tgz illustrates the bug, run mvn compile. The metamodel for the base class either needs a type param (and likewise the extends class on the sub-metamodel), or the base class needs to be generated with Object as the type -- 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, 6 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-528) MassIndexer attempts to index non-indexed subclasses of indexed types

by Sanne Grinovero (JIRA)

MassIndexer attempts to index non-indexed subclasses of indexed types --------------------------------------------------------------------- Key: HSEARCH-528 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-528 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.Final, 3.2.0.CR1, 3.2.0.Beta1 Reporter: Sanne Grinovero Fix For: 3.3.0 quoting comments from HSEARCH-526: j nadler : {quote}Sanne, I have @Indexed class Parent, @Indexed class Child1 extends Parent, @Indexed class Child2 extends Parent, unindexed class Child3 extends Parent. I create an indexer fullTextEntityManager.createIndexer(Parent.class), it seems that it then fetches all Parent entities. This includes all Child3 entities but Child3 is not indexed. It seems like the MassIndexer attempts to index them anyway. Best behavior might be to ignore these (explicitly check if the concrete subtype is @Indexed, skip that record if not, possibly log a warning) or as you say it could at least throw an error that makes it clear what the developer (me) did wrong. Thanks! {quote} Emmanuel Bernard : {quote}Ah, right. Sanne, you should use the same algorithm we use in the query building process to check the list of indexed subclasses to create the list of indexes to merge.{quote} -- 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, 6 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-457) Analyzers in Lucene 3.0 don't have a default constructor

by Sanne Grinovero (JIRA)

Analyzers in Lucene 3.0 don't have a default constructor -------------------------------------------------------- Key: HSEARCH-457 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-457 Project: Hibernate Search Issue Type: Sub-task Components: analyzer Reporter: Sanne Grinovero we're going to need a factory of analyzers or something; could be nice to use "simple" names to embed support for the most common analyzers (the advanced anaylzers are probably most commonly picked from Solr). Analyzers like StopWords where needing parameters anyway to make sense. -- 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, 6 months

4
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 September 2010