November 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-1829) Allow join on any property using property-ref

by Daljeet Singh Sarna (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=c... ] Daljeet Singh Sarna commented on HHH-1829: ------------------------------------------ We also waited for this to fix, and tried various option but it won't work. so we downloaded the source code and edited and compiled again and used the jar The changes wrere done to hibernate 3.2 Hibernate Changelog =================== Chages in version 3.2.1 (2006.11.16) ------------------------------------------- ** Bug # 1 * Comment out Exception stack trace in 'org.hibernate.transaction.JDBCTransaction' class at Line # 198 * Original code: log.error("Could not toggle autocommit", sqle); * New Code: log.error("Could not toggle autocommit"); ** Bug # 2 * Comment Fix to allow <join> to map key to different column of parent using property-ref, * Please refer to following site for patch details http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829 * File Name : org.hibernate.persister.entity.AbstractEntityPersister, * org.hibernate.cfg.HbmBinder, * org.hibernate.mapping.KeyValue, * org.hibernate.mapping.SimpleValue * Change log : Pleas refer to File "PatchInformation/hhh-1829.patch" ** Bug # 3 * Comment Fix to allow <join> to be used with class attribute entity-name * File Name : org.hibernate.cfg.HbmBinder * Original Code : line number 995,996 Property prop = createProperty( value, propertyName, persistentClass .getEntityName(), subnode, mappings, inheritedMetas ); * New Code: line number 995,996 Property prop = createProperty( value, propertyName, persistentClass .getClassName(), subnode, mappings, inheritedMetas ); > Allow join on any property using property-ref > --------------------------------------------- > > Key: HHH-1829 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829 > Project: Hibernate Core > Issue Type: New Feature > Components: metamodel > Affects Versions: 3.2.0 cr1, 3.2.0.cr2 > Reporter: Maarten Winkels > Assignee: Steve Ebersole > Attachments: AbstractJoinTest.java, HHH-1829-mwinkels.patch, hhh-1829.patch, JoinNoPropertyRefTest.java, JoinPropertyRefTest.java, Person.hbm.xml, Person.java, PersonNoPropertyRef.hbm.xml > > > Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is ignored. -- 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
0
0 / 0

[Hibernate-JIRA] Created: (EJB-400) Allow specification of CacheMode on EntityManager creation

by Chris Bredesen (JIRA)

Allow specification of CacheMode on EntityManager creation ---------------------------------------------------------- Key: EJB-400 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-400 Project: Hibernate Entity Manager Issue Type: Improvement Components: Documentation, EntityManager Reporter: Chris Bredesen Assignee: Chris Bredesen Priority: Minor Hibernate core allows specification of CacheMode at the Session level. In order to use this feature from JPA, it's necessary to modify the underlying Session using em.getDelegate(). This can be achieved in a more generic way by passing a property like "org.hibernate.cacheMode" to createEntityManagerFactory(Map). This should also be usable from @PersistenceContext. -- 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
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1829) Allow join on any property using property-ref

by michael cooper (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=c... ] michael cooper commented on HHH-1829: ------------------------------------- Hello, I was wondering if anyone can help me with this issue. I have been tearing my hair out all morning and I have stumbled across this, with some relief. Has it been resolved in any releases. If not is there a work-around. I have no idea how to use these patches. Would anyone be able to attach a jar file with this patch fixed or give me any pointers on it please. I have tried doing what was suggested here - http://jira.nhibernate.org/browse/NH-1040 , but to no avail Thanks in advance Mike > Allow join on any property using property-ref > --------------------------------------------- > > Key: HHH-1829 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829 > Project: Hibernate Core > Issue Type: New Feature > Components: metamodel > Affects Versions: 3.2.0 cr1, 3.2.0.cr2 > Reporter: Maarten Winkels > Assignee: Steve Ebersole > Attachments: AbstractJoinTest.java, HHH-1829-mwinkels.patch, hhh-1829.patch, JoinNoPropertyRefTest.java, JoinPropertyRefTest.java, Person.hbm.xml, Person.java, PersonNoPropertyRef.hbm.xml > > > Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is ignored. -- 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
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-274) Use Lucene's new readonly IndexReader

by Sanne Grinovero (JIRA)

Use Lucene's new readonly IndexReader ------------------------------------- Key: HSEARCH-274 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-274 Project: Hibernate Search Issue Type: Improvement Components: directory provider, documentation Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.1.0.CR1 # LUCENE-1329: Add optional readOnly boolean when opening an IndexReader. A readOnly reader is not allowed to make changes (deletions, norms) to the index; in exchanged, the isDeleted method, often a bottleneck when searching with many threads, is not synchronized. The default for readOnly is still false, but in 3.0 the default will become true. (Jason Rutherglen via Mike McCandless) In addition we should wrap the returned IndexReader to contain needed information to close it without having to search it back in synchronized hashmaps. -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-266) Do not switch to the current directory in FSSlaveDirectoryProvider if no file has bee copied

by Emmanuel Bernard (JIRA)

Do not switch to the current directory in FSSlaveDirectoryProvider if no file has bee copied -------------------------------------------------------------------------------------------- Key: HSEARCH-266 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-266 Project: Hibernate Search Issue Type: Improvement Components: directory provider Affects Versions: 3.1.0.Beta1 Reporter: Emmanuel Bernard This will allow IndexReaders to be reused longer. -- 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: (BVAL-23) Should Validator<T> be thread-safe?

by Emmanuel Bernard (JIRA)

Should Validator<T> be thread-safe? ----------------------------------- Key: BVAL-23 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-23 Project: Bean Validation Issue Type: Task Components: spec-general Reporter: Emmanuel Bernard Pros Can be reused easily across the board without thinking about it No real need to keep shared state Cons Contention issues? put constraint on the implementation -- 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
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-49) Mark metadata classes as immutable

by Emmanuel Bernard (JIRA)

Mark metadata classes as immutable ---------------------------------- Key: BVAL-49 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-49 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard -- 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-3588) RevisionType available via public API

by Scott Robidoux (JIRA)

RevisionType available via public API ------------------------------------- Key: HHH-3588 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3588 Project: Hibernate Core Issue Type: New Feature Components: envers Environment: Hibernate 3.2.6, envers 1.1.0.GA, Oracle 10g Reporter: Scott Robidoux Can you please create a public facing API so we can get Revision_Type value returned for a particular revision? It would be quite helpful to be able to see what type of revision the record is when retrieving all records. -- 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] Commented: (HHH-511) reattach object from same session

by Alex Pires de Camargo (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-511?page=co... ] Alex Pires de Camargo commented on HHH-511: ------------------------------------------- Patch for this fix probably generates HHH-3357 > reattach object from same session > --------------------------------- > > Key: HHH-511 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-511 > Project: Hibernate Core > Issue Type: Bug > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.4 > > Attachments: reattach-same-session.patch, reattach-same-session.patch > > > http://forum.hibernate.org/viewtopic.php?p=2231400#2231400 > There is a problem when you reattach a collection to the same session that it was previously attached to, after calling clear(). Hibernate checks the collections session reference, at reattach and concludes it is already attached. -- 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
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-140) Discriminator column not supported with JOINED strategy

by Constantine Voronin (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-140?page=co... ] Constantine Voronin commented on ANN-140: ----------------------------------------- I've the same problem with strategy=JOINED and Discriminator Values. It's very important to me to have *not null* value of discriminator field, I use it in group queries. Now I have to do in base classes something like: public MyBase () { // set the value of discriminator's field kind = this.getClass().getSimpleName(); } I think it is really ugly :( > Discriminator column not supported with JOINED strategy > ------------------------------------------------------- > > Key: ANN-140 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-140 > Project: Hibernate Annotations > Issue Type: Bug > Affects Versions: 3.1beta6 > Environment: Hibernate 3.1rc2, Hibernate Annotations 3.1b6 > Reporter: Steven Grimm > > Section 9.1.27 of the EJB3 persistence public draft says, "The DiscriminatorColumn annotation is used to define the discriminator column for SINGLE_TABLE and JOINED mapping strategies." But Hibernate ignores the DiscriminatorColumn annotation when the mapping strategy is JOINED; when a JOINED entity is persisted, its discriminator column is not included in the SQL "insert" statement, resulting in a not-null constraint violation if the discriminator column is marked NOT NULL in the database. > The JOINED strategy with discriminators is pretty ubiquitous in EJB3 sample code and tutorials out on the net, so lots of people are likely to run into this as they try out EJB3 for the first time. A few examples: > http://www.oracle.com/technology/tech/java/oc4j/ejb3/howtos-ejb3/howtoejb... > http://www.solarmetric.com/Software/Documentation/4.0.0EA/docs/full/html/... > http://www.caucho.com/resin-3.0/amber/tutorial/cmp-inherit/index.xtp -- 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
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2008