September 2006 - hibernate-issues

[Hibernate-JIRA] Updated: (ANN-303) Consider implementing @Entity(name=) through entityName

by James Olsen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-303?page=all ] James Olsen updated ANN-303: ---------------------------- Attachment: ANN-303-patch.txt Hibernate seems to be handling the Entity.name fine if entity-name is in the hbm.xml (I'm not currently using the annotations directly at runtime but using them to generate mapping files) it's just that it doesn't get into the meta-model from the annotations. This looks like a fault in the EntityBinder to me, as per the attached file. (Sorry it isn't a proper patch, I'm working in a scratch area for various reasons). Making that first change raised a second issue with the HibernateMappingExporter regarding the file name used for generated files. The attachment includes a change for that also. With these two small mods I'm happily using the Entity.name rather than ClassName for queries. > Consider implementing @Entity(name=) through entityName > ------------------------------------------------------- > > Key: ANN-303 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-303 > Project: Hibernate Annotations > Type: Improvement > Components: binder > Reporter: Emmanuel Bernard > Priority: Minor > Attachments: ANN-303-patch.txt > > > I'm doubtful but this might be a solution > http://jroller.com/page/MikeSlattery?entry=workaround_for_entity_name_alias -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1015) Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table

by George Daswani (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015?page=c... ] George Daswani commented on HHH-1015: ------------------------------------- I just ran into this limitation earlier. Using a joined-subclass instead seems to generate the correct query. > Incorrect SQL generated when one-to-many foreign key is in a discriminated subclass table > ----------------------------------------------------------------------------------------- > > Key: HHH-1015 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1015 > Project: Hibernate3 > Type: New Feature > Components: core > Versions: 3.1 beta 2 > Environment: Hibernate versions 3.1 beta 3 and 3.0.5 > Reporter: Steven Grimm > Priority: Minor > > > I have the following mappings describing a hierarchy of events and a class that the events refer to: > <hibernate-mapping package="com.xyz"> > <class name="Event" table="event" discriminator-value="-1"> > <id name="Id" type="long" column="event_id"/> > <discriminator column="event_type_id" type="integer" /> > <subclass name="EventPayer" discriminator-value="-3"> > <join table="event_payer"> > <key column="event_id" /> > <many-to-one name="payer" column="payer_id" class="Payer" /> > </join> > <subclass name="EventPayerCreated" discriminator-value="1" /> > </subclass> > </class> > <class name="Payer" table="payer"> > <id name="payerId" column="payer_id" type="java.lang.Long"/> > <set name="eventPayers" inverse="true" cascade="save-update"> > <key column="payer_id"/> > <one-to-many class="EventPayer"/> > </set> > </class> > </hibernate-mapping> > When I fetch the Payer.eventPayers collection, Hibernate generates this SQL: > select eventpayer0_.payer_id as payer7_1_, > eventpayer0_.event_id as event1_1_, > eventpayer0_.event_id as event1_5_0_, > eventpayer0_1_.payer_id as payer2_6_0_, > eventpayer0_.event_type_id as event2_5_0_ > from event eventpayer0_ > inner join event_payer eventpayer0_1_ > on eventpayer0_.event_id=eventpayer0_1_.event_id > where eventpayer0_.payer_id=? > The problem is that there is no event.payer_id column; payer_id is in the child table, not the parent. It appears that specifying a discriminated subclass in <one-to-many> is the same as specifying the superclass, or that Hibernate is ignoring the subclass's <join> element. As far as I can tell, this leaves no way to resolve bidirectional associations where one end of the association is in a discriminated subclass, which seems like a perfectly reasonable thing to want to do. > I also tried changing <key column="payer_id"/> to <key property-ref="payer"/> in the Payer class's <set> element, but got similar behavior in the form of a "property not found" error: Hibernate is either looking in the superclass's properties rather than the subclass's or is ignoring the list of properties in the <join> element. -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HB-520) Add Distinct to Criteria API

by Paul Malolepsy (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HB-520?page=com... ] Paul Malolepsy commented on HB-520: ----------------------------------- Has there been any more progress on this one? The only "workaround" for this that I've been able to come up with is to issue two queries from the criteria same criteria object. The first one gets the id's the second one is contrained to the ids. //set up crtieria as you wish, including pagination myCriteria = doStuffToSetupCriteria(); myCriteria.setFirstResult((page-1)*itemsPerPage); myCriteria.setMaxResults(itemsPerPage); //get the list if primary keys myCriteria.setProjection(Projections.distinct(Projections.property("myAllias.id")); List ids = gacc.list(); //now add the id's into the restriction myCriteria.add(Restrictions.in("myAlias.id, ids)); //clean up from the last critiera run gacc.setProjection(null); gacc.setFirstResult(0); gacc.setMaxResults(Integer.MAX_VALUE); //your results List objects = gacc.list() A little hacky I agree, but the only acceptable soltion I could find given this limitiation. > Add Distinct to Criteria API > ---------------------------- > > Key: HB-520 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-520 > Project: Hibernate2 > Type: New Feature > Components: core > Versions: 2.1 rc1 > Environment: Hibernate 2.1+, (Any DB) > Reporter: Stephen Owens > Priority: Minor > > > Need the ability to specify that results of a Criteria query should be 'DISTINCT', especially when joining to a collection. So the Criteria equivalent of the HQL statement > "select distinct parent from Parent as parent join Parent.children as child where child.age>5" -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (EJB-160) Push EJB3Configuration and SessionFactory into JNDI

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-160?page=co... ] Emmanuel Bernard commented on EJB-160: -------------------------------------- a core update shouldn't be needed for this one > Push EJB3Configuration and SessionFactory into JNDI > --------------------------------------------------- > > Key: EJB-160 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-160 > Project: Hibernate Entity Manager > Type: New Feature > Components: EntityManager > Reporter: Christian Bauer > Priority: Blocker > Fix For: 3.2.0.cr2 > > -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (ANN-368) Keywords first letter is not decapilalized

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-368?page=all ] Emmanuel Bernard updated ANN-368: --------------------------------- Component: lucene (was: binder) > Keywords first letter is not decapilalized > ------------------------------------------ > > Key: ANN-368 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-368 > Project: Hibernate Annotations > Type: Bug > Components: lucene > Versions: 3.2.0.cr1 > Reporter: Emmanuel Bernard > Priority: Trivial > Fix For: 3.2.0.cr2 > > > This does break backward compatibility -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (EJB-223) Configuration no longer Serializable

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-223?page=all ] Steve Ebersole moved HHH-2056 to EJB-223: ----------------------------------------- Project: Hibernate Entity Manager (was: Hibernate3) Key: EJB-223 (was: HHH-2056) Component: EntityManager (was: core) Version: (was: 3.2.0.cr4) > Configuration no longer Serializable > ------------------------------------ > > Key: EJB-223 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-223 > Project: Hibernate Entity Manager > Type: Bug > Components: EntityManager > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > > > EntityNotFoundDelegate is not serializable, preventing the configuration to serializa properly. > This block the Configuration optimization and the JNDI push -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-211) JavaDoc the EJB 3 API

by Emmanuel Bernard (JIRA)

JavaDoc the EJB 3 API --------------------- Key: EJB-211 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-211 Project: Hibernate Entity Manager Type: Improvement Components: Documentation Versions: 3.2.0.cr1 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor Fix For: 3.2.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

18 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Moved: (HHH-2057) Add "remove" cascading style to CascadeStyle for XML mappings

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2057?page=all ] Emmanuel Bernard moved EJB-222 to HHH-2057: ------------------------------------------- Project: Hibernate3 (was: Hibernate Entity Manager) Key: HHH-2057 (was: EJB-222) Component: core (was: EntityManager) > Add "remove" cascading style to CascadeStyle for XML mappings > ------------------------------------------------------------- > > Key: HHH-2057 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2057 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Christian Bauer > Fix For: 3.2.1 > > > Currently the AnnotationBinder translates a JPA CascadeType.REMOVE as follows: > case REMOVE: > cascade.append( "," ).append( "delete" ); > However, if I use XML mapping files I have to use cascade="delete" to get the same effect. A practical example why this is very inconvenient for users, documentation, etc: I want to translate the following annotation mapping to XML: > @OneToMany(cascade = { CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REMOVE}) > I end up with: > <set name="foo" cascade="persist, merge, delete"> > I recommend adding "remove" as an alias for "delete" to the map in engine/CascadeStyle.java -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1585) An instrumented persistent class reckons that a referenced non persistent class is also instrumented

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1585?page=all ] Steve Ebersole closed HHH-1585: ------------------------------- Resolution: Duplicate Exactly. This is one of the situations that was fixed as part of the mods for HHH-1931 > An instrumented persistent class reckons that a referenced non persistent class is also instrumented > ---------------------------------------------------------------------------------------------------- > > Key: HHH-1585 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1585 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.2 > Environment: Java 1.4.2, Win2000 > Reporter: Peter Schütt > Assignee: Scott Marlow > Attachments: InstrumentTask.patch > > > I have a persistent class, which is instrumented because we use access by field. > This persistent class refers to a non persistent class, which has only public fields: > public class NonPersistentClass > { > public int field1; > public String field2; > } > This class is not declared in a mapping file and is not instrumented. > ... > The persistent class reckon that "NonPersistentClass" is instrumented. > Decompiled code from Persistent class: > NonPersistentClass obj = new NonPersistentClass(); > obj.$cglib_write_field1(1); > ... > String s = obj.$cglib_read_field2(); > This is a severe 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1585) An instrumented persistent class reckons that a referenced non persistent class is also instrumented

by Igor Lobanov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1585?page=c... ] Igor Lobanov commented on HHH-1585: ----------------------------------- We just encountered the same problem, which is gone after switching to Hibernate 3.2CR4. So, it seems that fix made to HHH-1931 actually addresses current issue. > An instrumented persistent class reckons that a referenced non persistent class is also instrumented > ---------------------------------------------------------------------------------------------------- > > Key: HHH-1585 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1585 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.1.2 > Environment: Java 1.4.2, Win2000 > Reporter: Peter Schütt > Assignee: Scott Marlow > Attachments: InstrumentTask.patch > > > I have a persistent class, which is instrumented because we use access by field. > This persistent class refers to a non persistent class, which has only public fields: > public class NonPersistentClass > { > public int field1; > public String field2; > } > This class is not declared in a mapping file and is not instrumented. > ... > The persistent class reckon that "NonPersistentClass" is instrumented. > Decompiled code from Persistent class: > NonPersistentClass obj = new NonPersistentClass(); > obj.$cglib_write_field1(1); > ... > String s = obj.$cglib_read_field2(); > This is a severe 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

18 years, 3 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 September 2006