August 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2477) lazy fetching ManyToOne produces inproper proxies when using single table inheritance strategy

by Daniel Nguyen (JIRA)

lazy fetching ManyToOne produces inproper proxies when using single table inheritance strategy ---------------------------------------------------------------------------------------------- Key: HHH-2477 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2477 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: hibernate 3.2.1-GA, postgresql 8.1 Reporter: Daniel Nguyen Attachments: bug.zip I have entity base class Vehicle and entity class Car which extends Vehicle (using single table inheritance strategy). I also have entity class User which have single-ended @ManyToOne relation from User to Vehicle with lazy fetching. Now there is a Car instance "c" and User instance "u" with relation to "c". Lazily fetching vehicle from "u" results with proxy object "o" which is instanceof Vehicle but not instanceof Car as expected. So it's impossible cast "o" to Car or at least read any of Car's property from "o". This is serious problem when inheritance is extensively used because inproper proxy object remains in cache. To walkaround I'd have to resign with lazy fetching (much performance loss) or manually replace proxy object in cache. testing code: SessionFactory sf = null; Session s = null; Transaction tx = null; try { sf = cfg.buildSessionFactory(); s = sf.openSession(); tx = s.beginTransaction(); //create car Car car = new Car(); car.setIdVehicle(1); car.setAge(5); s.save(car); //create user of car User user = new User(); user.setIdUser(1); user.setVehicle(car); s.save(user); //make sure it is actually added s.flush(); // test 1 - works ok, because we loaded vehicle before user s.clear(); //clear cache Vehicle vv = (Vehicle)s.get(Vehicle.class, 1); User uu = (User)s.get(User.class, 1); //we know that user vehicle is actually a Car Car cc = (Car)uu.getVehicle(); // test 2 - fails, when using lazy fetching s.clear(); //clear cache User u = (User)s.get(User.class, 1); Vehicle v = u.getVehicle(); //we know that user vehicle is actually a Car //so we cast to Car but ClassCastException is raised!!! Car c = (Car)v; //let's check what's actual class of v System.out.println(v.getClass().getName()); System.out.println(v.getClass().getSuperclass().getName()); //result: // test.hibernate.Vehicle$$EnhancerByCGLIB$$12ce1883 // test.hibernate.Vehicle //but I expected: // test.hibernate.Car$$EnhancerByCGLIB$$xxxxx // test.hibernate.Car } finally { if (tx!=null) tx.rollback(); if (s!=null) s.close(); if (sf!=null) sf.close(); } -- 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

16 years, 4 months

7
10
0 / 0

[Hibernate-JIRA] Created: (ANN-769) Ignore unmapped enum values - org.hibernate.type.EnumType throws exceptions when trying to map unknown values to an Enum

by Alvin (JIRA)

Ignore unmapped enum values - org.hibernate.type.EnumType throws exceptions when trying to map unknown values to an Enum ------------------------------------------------------------------------------------------------------------------------ Key: ANN-769 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-769 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.4.0.GA Reporter: Alvin The issue is described in a previous Jira - http://opensource.atlassian.com/projects/hibernate/browse/ANN-717. To solve this particular scenario could we add either (unless someone has a more correct method) - - an attribute to the @Enumerated annotation so that ignores values in the database which are not mapped via the Enum - extend @NotFound annotation so it also works on enums -- 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

16 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-465) order by nulls first / last

by Brooks Lyrette (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-465?page=co... ] Brooks Lyrette commented on HHH-465: ------------------------------------ Thanks for the Interceptor Emilio but you missed two important cases. You have to watch our for 'limit' statements if paging is used and also for functions upper(column_name) > order by nulls first / last > --------------------------- > > Key: HHH-465 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-465 > Project: Hibernate3 > Issue Type: Improvement > Components: core > Affects Versions: 3.0.3 > Reporter: Anthony Patricio > Priority: Minor > Attachments: CustomNullsFirstInterceptor.java > > > support of nulls first / last in order clause > "NULLS LAST" is part of the SQL 99 standard. > The syntax is as follows: > ORDER BY [COLUMN NAME] [ASC | DESC] [NULLS FIRST | NULLS LAST] > In different DBs, the sorting of nulls relative to other values is handled differently. > PostgreSQL - Nulls are considered HIGHER than non-nulls. > DB2 - Higher > MSSQL - Lower > MySQL - Lower > Oracle - Higher > The following DBs have supported this functionality: > DB2 V7 > Oracle 9i > PostgreSQL, MySQL, SQLServer do not appear to support this from what I can gather. > see http://forum.hibernate.org/viewtopic.php?t=942176&start=0&postdays=0&post... -- 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

16 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-930) hbm2ddl: no outpufile on update="true"

by Nick Folder (JIRA)

hbm2ddl: no outpufile on update="true" -------------------------------------- Key: HBX-930 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-930 Project: Hibernate Tools Issue Type: Bug Components: ant Affects Versions: 3.2beta9 Environment: Hibernat 3.2, Oracle9i Reporter: Nick Folder Priority: Minor No outputfile is generated when option update is set to true. Example: <hbm2ddl export="false" outputfilename="sql.ddl" update="true" /> Thanks B -- 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

16 years, 4 months

4
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1589) Querytime logging

by Lars Torunski (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1589?page=c... ] Lars Torunski commented on HHH-1589: ------------------------------------ Use can use p6spy or http://www.alvinsingh.org/blog/2008/06/hibernate-query-performance-logging/ , but logging query times would be great. > Querytime logging > ----------------- > > Key: HHH-1589 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1589 > Project: Hibernate3 > Issue Type: New Feature > Affects Versions: 3.1.3 > Reporter: Joris Verschoor > Priority: Trivial > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > It'd be nice to have hibernate log query times (time to from execute to first result, from first to last result, total time) when sql logging is enabled > Right now we're using profiling tools, but sometimes you don't have any tools available, and doing logging around every query is tedious -- 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

16 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-723) Impossible to bind a SortedMap collection

by Alexandre Dutra (JIRA)

Impossible to bind a SortedMap collection ----------------------------------------- Key: ANN-723 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-723 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: hibernate: 3.2.5.ga hibernate-annotations: 3.3.0.ga database: HSQL 1.8.0.7 Reporter: Alexandre Dutra Priority: Minor See http://forum.hibernate.org/viewtopic.php?t=976437 I have the following collection declared in a persistent class: @CollectionOfElements @Sort(type = SortType.NATURAL) @JoinTable(name = "delivery_option_price", joinColumns = @JoinColumn(name = "delivery_option_id")) private SortedMap<Float, MonetaryAmount> prices = new TreeMap<Float, MonetaryAmount>(); Hibernate fails to bind it to a database table. The stack trace is: java.lang.NullPointerException at org.hibernate.cfg.annotations.MapBinder.bindKeyFromAssociationTable(MapBinder.java:129) at org.hibernate.cfg.annotations.MapBinder.access$000(MapBinder.java:53) at org.hibernate.cfg.annotations.MapBinder$1.secondPass(MapBinder.java:83) at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:43) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1130) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:316) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) ... A workaround to this is to explicitly specify the map key class by adding a org.hibernate.annotations.MapKey annotation: @org.hibernate.annotations.MapKey(targetElement = Float.class, columns = @Column(name = "WEIGHT")) Browsing the source code, I realized that the NullPointerException is being raised beacause the following method returns null in org.hibernate.annotations.common.reflection.java.JavaXCollectionType: public XClass getMapKey() { return new TypeSwitch<XClass>() { @Override public XClass caseParameterizedType(ParameterizedType parameterizedType) { if ( getCollectionClass().isAssignableFrom( Map.class ) ) { return toXClass( parameterizedType.getActualTypeArguments()[0] ); } return null; } }.doSwitch( approximate() ); } More specifically, the following expression seems misconstructed: getCollectionClass().isAssignableFrom( Map.class ) The correct expression would be: Map.class.isAssignableFrom( getCollectionClass() ) At least if, as I understand it, the goal is to determine whether the collection class is or is not a Map in anyone one of its implementations. The same applies to the getElementClass() method, in the same class. If my analyzis is correct, the bug might be very easy to fix, but maybe I'm underestimating its impacts. -- 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

16 years, 4 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3448) replace instruction for SQLServerDialect

by Anthony Patricio (JIRA)

replace instruction for SQLServerDialect ---------------------------------------- Key: HHH-3448 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3448 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Anthony Patricio Priority: Trivial add registerFunction( "replace", new StandardSQLFunction("replace", Hibernate.STRING) ); to SQLServerDialect. -- 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

16 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3447) A typo in the documentation

by Behrang Saeedzadeh (JIRA)

A typo in the documentation --------------------------- Key: HHH-3447 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3447 Project: Hibernate3 Issue Type: Bug Components: documentation Affects Versions: 3.3.0.GA Reporter: Behrang Saeedzadeh Priority: Trivial In "1.2. Part 1" , the following sentence: We use [b]an[/b] Java database (HSQL DB), so we do not have to install any database server. should be changed to: We use [b]a[/b] Java database (HSQL DB), so we do not have to install any database server. -- 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

16 years, 4 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3446) In bidirectional remove element from detached collection and merge it will not update the many side

by Avihai Marchiano (JIRA)

In bidirectional remove element from detached collection and merge it will not update the many side --------------------------------------------------------------------------------------------------- Key: HHH-3446 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3446 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Windows Reporter: Avihai Marchiano Attachments: persistence-deps.zip In bidirectional when remove element from the collection (i also nullify the reference from the many side ) the element reference wasnt nullify. i have a detached collection (user has many permissions) in detached i call to : permission.user = null; iterator.remove(); and then call to em.merge(user); it dosnt nullify the FK in permission table. if i remark the line - "iterator.remove();" then it will nullify the FK, but in bi-directional you update both sides of the collection in order to be consistent. attached a project. -- 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

16 years, 4 months

1
0
0 / 0

[Hibernate-JIRA] Deleted: (HHH-1636) Removed trace in LazyInitializationException constructor(s)

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1636?page=c... ] Steve Ebersole deleted HHH-1636: -------------------------------- > Removed trace in LazyInitializationException constructor(s) > ----------------------------------------------------------- > > Key: HHH-1636 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1636 > Project: Hibernate3 > Issue Type: Task > Reporter: jose > Original Estimate: 1 minute > Remaining Estimate: 1 minute > > Problem: The trace confuse my log traces with "inexistent" errors (my code captured and process this exception) > Solution: Supress the constructor trace (imagine that all Java exceptions show messages in their constructors...). The exception is launched and propagated... > Note: Log Trace is "failed to lazily initialize a collection of role: es.bfc.example.music.Artist.albums, no session or session was closed" -- 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

16 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2008