May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-1134) subclass tag with discriminator in one to many mapping

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134?page=c... ] Gail Badner commented on HHH-1134: ---------------------------------- Could this be related to HHH-4953? > subclass tag with discriminator in one to many mapping > ------------------------------------------------------ > > Key: HHH-1134 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134 > Project: Hibernate Core > Issue Type: Bug > Components: core > Environment: hibernate 3.0.5, Oracle > Reporter: Dilip Ranjith > > Consider the following hbm.xml file > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping > > > <class > name="DCDTO" > table="ACCDC" > dynamic-update="true" > > > <id > name="ID" > type="java.lang.String" > > > <column > name="DCINFOID" > /> > <generator class="sequence"> > <param name="sequence">DSEQ</param> >  > </generator> > </id> > <discriminator > column="accountType" > not-null="true" > type="java.lang.String" > force="true" > insert="true" > /> > <property > name="creditMax" > type="java.lang.Double" > update="true" > insert="true" > column="creditMax" > /> > <subclass > name="CDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="C" > > > </.subclass> > <subclass > name="DDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="D" > > > </.subclass> > </class> > </hibernate-mapping> > DCDTO is the super class while DDTO and CDTO are its child classes > If in a mapped object say TDTO there are a set of CDTOs and a separate set of DDTOs > when we get TDTO the where clause "where accountType='D' " is not there when the query for set of DDTOs are generated. so instead of a set of DDTOs i am getting a set of both DDTO's and CDTO's -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4786) SerializableType + custom Serializable class + L2 cache causes problems

by Steve Ebersole (JIRA)

SerializableType + custom Serializable class + L2 cache causes problems ----------------------------------------------------------------------- Key: HHH-4786 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4786 Project: Hibernate Core Issue Type: Bug Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Beta-3 The changes done for HHH-2990 cause an issue when users map non-JDK Serializable classes using SerializableType in combination with attempting to cache those values into second level cache. SerializableType reports the classloader to use for deserialization as the classloader of java.io.Serializable (which is generally null indicating the "bootstrap class loader"). However that classloader will (generally) not have visibility into the classloader needed to see these non-JDK classes. -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1134) subclass tag with discriminator in one to many mapping

by HG (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134?page=c... ] HG commented on HHH-1134: ------------------------- Well force="true" will solve the issue, but not if you use second level cache. While fetching the entity from a cache hibernate does not care if the force is true or not, simply because of the fact that discriminator information is not present in the CacheKey used by hibernate. What can we do to have to have the same behaviour as "force='true'" with second level cache :( ??? > subclass tag with discriminator in one to many mapping > ------------------------------------------------------ > > Key: HHH-1134 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1134 > Project: Hibernate Core > Issue Type: Bug > Components: core > Environment: hibernate 3.0.5, Oracle > Reporter: Dilip Ranjith > > Consider the following hbm.xml file > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE hibernate-mapping PUBLIC > "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping > > > <class > name="DCDTO" > table="ACCDC" > dynamic-update="true" > > > <id > name="ID" > type="java.lang.String" > > > <column > name="DCINFOID" > /> > <generator class="sequence"> > <param name="sequence">DSEQ</param> >  > </generator> > </id> > <discriminator > column="accountType" > not-null="true" > type="java.lang.String" > force="true" > insert="true" > /> > <property > name="creditMax" > type="java.lang.Double" > update="true" > insert="true" > column="creditMax" > /> > <subclass > name="CDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="C" > > > </.subclass> > <subclass > name="DDTO" > dynamic-update="true" > dynamic-insert="true" > discriminator-value="D" > > > </.subclass> > </class> > </hibernate-mapping> > DCDTO is the super class while DDTO and CDTO are its child classes > If in a mapped object say TDTO there are a set of CDTOs and a separate set of DDTOs > when we get TDTO the where clause "where accountType='D' " is not there when the query for set of DDTOs are generated. so instead of a set of DDTOs i am getting a set of both DDTO's and CDTO's -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-324) Default annotation not executing when group selector activated

by Marc Schipperheyn (JIRA)

Default annotation not executing when group selector activated -------------------------------------------------------------- Key: HV-324 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-324 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.1.0.Beta1 Reporter: Marc Schipperheyn Assignee: Hardy Ferentschik Attachments: RegistrationVO.java When you call the validate function with a non-default group selector active, the default constraints do not execute. AFAIC this is unexpected behaviour. Default constraints by their very nature should always execute. Also, since it's very easy to exclude default execution by applying a non-default group selector. If this is in fact a design decision then the documentation should make very, *very* clear (e.g. through one of those "Notes": Default constraints do NOT execute when a group selector is active! If you want the default to be executed, also add Default.class to the set of group selectors you specify) that default constraints do not execute when a group constraint is active. It doesn't at the moment and I was caught by surprise. -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-820) TypeDef does not work when used on @Embeddable or @MappedSuperClass classes.

by Ted Bergeron (JIRA)

TypeDef does not work when used on @Embeddable or @MappedSuperClass classes. ---------------------------------------------------------------------------- Key: ANN-820 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-820 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Environment: Oracle 11, hibernate 3.4.0 GA Reporter: Ted Bergeron @TypeDefs({ @TypeDef( name = "status", typeClass = EnumUserType.class, parameters = {@Parameter(name = "enumClass", value = "com.acme.common.model.Status")} ) }) I declare various @TypeDefs such as this. They all work fine when used in @Entity classes. When used in a @MappedSuperclass, or an @Embeddable, they fail. I see from the docs that these are global and double checked that I do not have any duplicate @TypeDef definitions. -- 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, 11 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5232) Use intern() to reuse strings and reduce memory usage / save 6%

by Yves Galante (JIRA)

Use intern() to reuse strings and reduce memory usage / save 6% ---------------------------------------------------------------- Key: HHH-5232 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5232 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.6 Environment: Hibernate 3.6.0-SNAPSHOT Linux x86_64 Bits Reporter: Yves Galante Priority: Minor Attachments: DuplicateString.patch This patch is an update of JIRRA HHH-3924 for Hibernate 3.6. Testsuite executed without new failures. Resume of the original JIRRA HHH-3924 : >>DefaultEntityAliases suffix and rowIdAliases String fields are not interned as are other fields in the class. This leads to significant >>of memory usage on our application. >>BasicLoader suffixes and QueryLoader sqlAliasSuffixes can also be interned so as to save more memory See the detailed result of this patch : ======================================== Test conditions ======================================== Hibernate version : 3.6.0-SNAPSHOT Yourkit : 8.0 OS : Linux x86_64 Bits. Test case : org.hibernate.test.legacy.ParentChildTest.testReplicate() Time : Memory snapshot is taken at the of the test. ======================================== Result before patch ======================================== SessionFactoryImpl size : 3939 KB Duplicates String example : "0_" : 452 duplicates (32KB) "rowid_0_" : 405 duplicates (32KB) "1_" : 145 duplicates (10KB) "rowid_1_" : 130 duplicates (10KB) ... "fee3_" : 65 duplicates (5KB) "glarch1_" : 55 duplicates (5KB) ... "foo2_2_5" : 46 duplicates (3KB) ... "string" : 28 duplicates (2KB) ======================================== Result after patch ======================================== SessionFactoryImpl size : 3688 KB Save 251 Kb, 6% of the session factory size. -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-323) URL Validator needs to pass on empty Strings

by Marc Schipperheyn (JIRA)

URL Validator needs to pass on empty Strings -------------------------------------------- Key: HV-323 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-323 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 4.1.0.Beta1 Reporter: Marc Schipperheyn Assignee: Hardy Ferentschik Priority: Minor The URL Validator passed on null Strings. However, in some cases the engines we use somestimes treat an empty form input as "" leading to a not null empty String. These should also validate true. -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-4401) @Formula(value="")

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401?page=c... ] Emmanuel Bernard updated HHH-4401: ---------------------------------- Fix Version/s: (was: 3.3.x) > @Formula(value="") > ------------------ > > Key: HHH-4401 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Assignee: Emmanuel Bernard > Priority: Trivial > > Support formula -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-4401) @Formula(value="")

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401?page=c... ] Emmanuel Bernard commented on HHH-4401: --------------------------------------- No it's very likely not. First of it's an annotations version not a core version and second I think it's much older than Annotations 3.4 or 3.3 but I did not do the archeology. At any rate it's very old. > @Formula(value="") > ------------------ > > Key: HHH-4401 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4401 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Assignee: Emmanuel Bernard > Priority: Trivial > Fix For: 3.3.x > > > Support formula -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5226) Specify the error instead on general UnsupportedOperationException

by Rincy Rappai (JIRA)

Specify the error instead on general UnsupportedOperationException ------------------------------------------------------------------ Key: HHH-5226 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5226 Project: Hibernate Core Issue Type: New Feature Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, WebSphere 6.1.0.5, Windows XP, RAD 7.0.0.2, Oracle 10g Reporter: Rincy Rappai The API's in the class WebSphereExtendedJTATransactionLookup does not give a meaningful exception if there is an exception and the transaction fails. For any failure with the transaction the "UnsupportedOperationException" is thrown. There has been many links on this exception and a first look shows this as a bug with Hibernate. http://opensource.atlassian.com/projects/hibernate/browse/HHH-2457 http://opensource.atlassian.com/projects/hibernate/browse/HHH-2124 http://opensource.atlassian.com/projects/hibernate/browse/HHH-3111 http://opensource.atlassian.com/projects/hibernate/browse/HHH-1287 Need resolution to identify the error and throw the related exception instead on general UnsupportedOperationException. -- 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, 11 months

2
2
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 May 2010