June 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-1042) Make DocHelper robust against failing buildSettings()

by Arnout Engelen (JIRA)

Make DocHelper robust against failing buildSettings() ----------------------------------------------------- Key: HBX-1042 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1042 Project: Hibernate Tools Issue Type: Improvement Components: hbm2doc Reporter: Arnout Engelen Attachments: dochelper.diff.txt DocHelper calls cfg.buildSettings(). to get the Dialect, default catalog name and default schema name. However, cfg.buildSettings() may fail with a HibernateException (example below). It would be nice to have DocHelper handle this more gracefully. Attached is a simple patch that does this. (background: I'd like to use the Configuration I'm getting from a Spring LocalSessionFactoryBean, which after initial creation leaves its LocalDataSourceConnectionProvider in a state that yiels a HibernateException when calling 'configure()' on it, which buildSettings() does. Because of this issue, I cannot use the DocExporter for my Spring-based hibernate configurations) -- 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, 5 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-115) Add a default value for indexing null value

by Julien Brulin (JIRA)

Add a default value for indexing null value ------------------------------------------- Key: HSEARCH-115 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-115 Project: Hibernate Search Issue Type: Improvement Components: mapping Reporter: Julien Brulin Hi, Null elements are not indexed by lucene then it's not easy to use a nullable property in lucene query. I have a TagTranslation entity in my model with a nullable property language. In this case null is used as default language for tag translation. Each translation may have many variations like synonyms. Because I can specified a default value for null value in the @Field annotation like this @Field(index=Index.UN_TOKENIZED, store=Store.NO, default='null'), i can't search a cat tag with a default translation like this : +value:cat* +lang:null <pre></code> @Entity() @Table(name="indexing_tag_trans") @org.hibernate.annotations.Cache(usage=org.hibernate.annotations.CacheConcurrencyStrategy.READ_WRITE) @Indexed public class TagTranslation implements java.io.Serializable { private static final long serialVersionUID = -1065316566731456110L; @Id @GeneratedValue(strategy=GenerationType.IDENTITY) @DocumentId private Integer id; @Field(index=Index.UN_TOKENIZED, store=Store.NO) private String language; @Field(index=Index.TOKENIZED, store=Store.YES) private String value; @OneToMany(cascade=CascadeType.ALL, fetch=FetchType.LAZY) @org.hibernate.annotations.Fetch(org.hibernate.annotations.FetchMode.SUBSELECT) @JoinColumn(name="translation_id") @IndexedEmbedded private List<TagVariation> variations = new LinkedList<TagVariation>(); public TagTranslation() { } ... </code> </pre> What do you think about that ? Ps: sorry for english write, i am a french guy. -- 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, 5 months

4
28
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-119) Enable lucene similarity seach based on term frequency vector by QBE-like query

by Xin Wu (JIRA)

Enable lucene similarity seach based on term frequency vector by QBE-like query --------------------------------------------------------------------------------- Key: HSEARCH-119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-119 Project: Hibernate Search Issue Type: New Feature Reporter: Xin Wu Scenario: Your bookstore application needs a function as follow: When a user see a list of books, there is a similar books button for each book. If user clicks this button of one book item, the similar books will be listed. The similarity is evaluated by all terms in summary of the book and similarity score is dirived from Lucene search similarity package which uses term frequency vectors in calculation. It will compare the target in all corresponding documents in the index and return the hits in order. Note: this funtion is not same as fuzzy query which still needs a definite query condition. In the contrast, similarity search only needs one or several fields (of object/document)to be specified and the rest will be automatically caculated by lucene. A QBE-like API should be used to make such query. You can specify the fields in such query. Please see discussion about this topic in the forum: http://forum.hibernate.org/viewtopic.php?t=979692 -- 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, 5 months

3
8
0 / 0

[Hibernate-JIRA] Created: (ANN-668) Method in entity with return type of ArrayList<Object[]> causes failure to build session factory

by Clint Popetz (JIRA)

Method in entity with return type of ArrayList<Object[]> causes failure to build session factory ------------------------------------------------------------------------------------------------ Key: ANN-668 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-668 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.X, no database needed (happens during factory build before connecting to db) Reporter: Clint Popetz Attachments: propertyTypeExtractorBug.tar.gz The following source: @javax.persistence.Entity public class TestEntity { @javax.persistence.Id public int Id; public java.util.ArrayList<Object[]> badMethod() { return null; } public static void main(String args[]) { new org.hibernate.cfg.AnnotationConfiguration().addAnnotatedClass(TestEntity .class).configure().buildSessionFactory(); } } will cause: java.lang.IllegalArgumentException: No PropertyTypeExtractor available for type void at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.toXType(JavaReflectionManager.java:164)^M at org.hibernate.annotations.common.reflection.java.JavaXMethod.create(JavaXMethod.java:18) at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.getXMethod(JavaReflectionManager.java:128) at org.hibernate.annotations.common.reflection.java.JavaXClass.getDeclaredMethods(JavaXClass.java:114) at org.hibernate.validator.ClassValidator.initValidator(ClassValidator.java:214) at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:133) at org.hibernate.validator.event.ValidateEventListener.initialize(ValidateEventListener.java:91) at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:356) at org.hibernate.cfg.Configuration.getInitializedEventListeners(Configuration.java:1304) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) Changing the return type to List<Object[]> avoids the bug. Attached is a tgz of an ant-buildable project; typing "ant run" will illustrate the bug. -- 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, 5 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3144) Final methods preclude some useful Hibernate extensions

by Ali Ibrahim (JIRA)

Final methods preclude some useful Hibernate extensions ------------------------------------------------------- Key: HHH-3144 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3144 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Ali Ibrahim Priority: Minor The following methods are final: AbstractPersistentCollection#read, AbstractPersistentCollection#write, AbstractLazyInitializer#initialize. It can be useful to override these methods. Fix is to make them protected. -- 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, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-470) enrich UniqueConstraint with property name

by Johnny D. (JIRA)

enrich UniqueConstraint with property name ------------------------------------------ Key: ANN-470 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-470 Project: Hibernate Annotations Type: Improvement Reporter: Johnny D. To be able in annotation to give uniqueConstraint exact database name, there is need to add field java.lang.String name(); to annotation class UniqueConstraint in similar way like in index is. -- 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, 5 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2319) StatelessInterceptor

by Max Rydahl Andersen (JIRA)

StatelessInterceptor -------------------- Key: HHH-2319 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2319 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.1 Reporter: Max Rydahl Andersen It would make sense to have an Interceptor for StatelessSession to solve the following usecases: Log/adjust SQL: onPrepareStatement Proper entityname handling: instantiate/getEntity Maybe also tx interaction: afterTransationBegin/beforeTransactionCompletion/afterTransactionCompletion Technically it could be solved by just allowing to pass in a normal interceptor to a StatelessSession and just document that the state oriented callbacks will not be called. Alternatively we can create a StatelessInterceptor that only implement the releavant methods and wrap that instance into an internal Interceptor. -- 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, 5 months

2
1
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, 5 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, 5 months

7
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2835) Setting org.hibernate.type logging to debug produces no logging

by Jeremy Grodberg (JIRA)

Setting org.hibernate.type logging to debug produces no logging --------------------------------------------------------------- Key: HHH-2835 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2835 Project: Hibernate3 Issue Type: Bug Components: core, documentation Affects Versions: 3.2.5, 3.2.4 Environment: Hibernate 3.2.4.ga and Hibernate 3.2.5.ga with MySQL5Dialect (configured with Hibernate Annotations 3.3.0.ga and Spring 2.0.6) Reporter: Jeremy Grodberg Priority: Minor According to the online documentation (labeled as version 3.2.2 at this moment), Table 3.9 "Hibernate Log Categories", as viewed here today: http://www.hibernate.org/hib_docs/v3/reference/en/html/session-configurat... Setting the log4j category "org.hibernate.type" to debug should "Log all JDBC parameters". However, it produces no output at all. When I go on to set "org.hibernate" to debug, I get output like this: DEBUG: org.hibernate.jdbc.AbstractBatcher - about to open PreparedStatement (open PreparedStatements: 0, globally: 0) DEBUG: org.hibernate.SQL - select count(*) from album where genreID=? DEBUG: org.hibernate.loader.Loader - bindNamedParameters() 126 -> genreId [1] DEBUG: org.hibernate.jdbc.AbstractBatcher - about to open ResultSet (open ResultSets: 0, globally: 0) DEBUG: org.hibernate.loader.Loader - result row: DEBUG: org.hibernate.jdbc.AbstractBatcher - about to close ResultSet (open ResultSets: 1, globally: 1) DEBUG: org.hibernate.jdbc.AbstractBatcher - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) Note that the JDBC parameters are logged under org.hibernate.loader but nothing appears under org.hibernate.type. FYI, genreId is, in this case, a Long. Perhaps this is expected/desired when using annotations? If so, then please update the documentation. If not, please restore the logging. -- 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

10
10
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 2008