April 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2504) Incorrect SQL generated by Oracle/Oracle9 dialects when using composite IDs as keys

by Laurent Pireyn (JIRA)

Incorrect SQL generated by Oracle/Oracle9 dialects when using composite IDs as keys ----------------------------------------------------------------------------------- Key: HHH-2504 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2504 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Java 1.4/1.5, Windows XP, Oracle 8/9/10 Reporter: Laurent Pireyn This issue is a clone of HHH-683, which has been rejected without any explanation. The problem described then is still very annoying... -- 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, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2496) Parameter binding in wrong order when filter adds params

by David Sheldon (JIRA)

Parameter binding in wrong order when filter adds params -------------------------------------------------------- Key: HHH-2496 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2496 Project: Hibernate3 Type: Bug Components: query-hql Environment: Hibernate version: 3.2 Database: Postgresql 8.1.6 Reporter: David Sheldon it seems that if you use a filter in the "order by" clause of your query, it binds the parameters in the wrong order. I've been looking through the code, and couldn't work out where the binding of filter parameters take place. Am I doing something wrong here, or is this a bug? I don't get an exception, but the query returns the wrong data because the parameters are sent to the database in the wrong order. Mapping documents: <hibernate-mapping> <class name="bug.Event" table="events"> <id name="id" column="event_id"> <generator class="native"/> </id> <property name="date" type="timestamp" column="timestamp" /> </class> <class name="bug.Thing" table="things"> <id name="id" column="id"> <generator class="native"/> </id> <property name="name" type="string" /> <list name="events" lazy="true" table="things_to_events" cascade="save-update,delete,delete-orphan"> <key column="thing_id"/> <list-index column="index"/> <many-to-many class="bug.Event" column="event_id"/> <filter name="dateFilter" condition="event_id in (select events.event_id from events where events.timestamp between :startDate and :endDate)"/> </list> </class> <filter-def name="dateFilter"> <filter-param name="startDate" type="date"/> <filter-param name="endDate" type="date"/> </filter-def> </hibernate-mapping> Code between sessionFactory.openSession() and session.close(): Thing t = new Thing(); t.setName("bob"); Event e = new Event(); e.setDate(new Date()); t.setEvents(Collections.singletonList(e)); session.save(e); session.save(t); session.enableFilter("dateFilter").setParameter("startDate", new GregorianCalendar(2007, 1, 20).getTime()).setParameter("endDate", new GregorianCalendar(2007, 2, 20).getTime()); Query query = session.createQuery("From Thing Where name = :name order by size(events)"); query.setParameter("name", "bob"); System.err.println("Size: " + query.list().size()); The generated SQL (show_sql=true): Hibernate: select thing0_.id as id1_, thing0_.name as name1_ from things thing0_ where thing0_.name=? order by (select count(events1_.thing_id) from things_to_events events1_ where thing0_.id=events1_.thing_id and events1_.event_id in (select events.event_id from events where events.timestamp between ? and ?)) Debug level Hibernate log excerpt: [java] 11:21:31,176 DEBUG AbstractBatcher:476 - preparing statement [java] 11:21:31,177 DEBUG DateType:133 - binding '20 February 2007' to parameter: 1 [java] 11:21:31,178 DEBUG DateType:133 - binding '20 March 2007' to parameter: 2 [java] 11:21:31,179 DEBUG StringType:133 - binding 'bob' to parameter: 3 As you can see, "bob" should be bound to parameter 1, 20th Feb to 2, and 20th March to 3. -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2018) Cannot map views in postgres unless hbm2ddl.auto is unset

by Dave E Martin (JIRA)

Cannot map views in postgres unless hbm2ddl.auto is unset --------------------------------------------------------- Key: HHH-2018 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2018 Project: Hibernate3 Type: Bug Versions: 3.2.0.cr2 Environment: hibernate 3.2cr2 annotations 3.2cr1 postgresql 8.1 with postgresql-8.1-404.jdbc3.jar This is also a problem in hibernate 3.1 Reporter: Dave E Martin Attempting to map a view with hibernate results in: Exception in thread "main" org.hibernate.HibernateException: Missing table: monthly_block_totals_utc Even though this exists (as a view) in the database. making sure hbm2ddl.auto is not set allows the application to work, but at the expense of being unable to update or validate the schema (or allow the end user to control whether the schema should be updated or not). Furthermore, there doesn't appear to be a 'none' or any documented way to set .auto to something which would be the equivalent of it not being set. (or to clear it out of the properties, and setting it to null doesn't work either). This appears to be related to HHH-1329 and HHH-1473. Stepping into the process reveals that postgres apparently reports views as views and not tables, causing them to be overlooked by Hibernate when its validating. -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2490) ClassCastException causes a logging statement to throw another ClassCastException upon inconsistent instantiation of NullableType

by Øyvind Roth (JIRA)

ClassCastException causes a logging statement to throw another ClassCastException upon inconsistent instantiation of NullableType --------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2490 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2490 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: MS SQLServer Windows 2000 Java 1.5.0_10 Reporter: Øyvind Roth (Have me excused that I don't know well the internalities of Hibernate, but I think that you get the point from some kind of "bird's perpective" anyhow). My pojo is defined in my xml mapping with a column/field as follows: ... <property name="encrypted" type="string" column="encrypted" insert="true" update="true" not-null="true"/> ... The corresponding POJO class is defined with two access methods: String getEncrypted(); and boolean isEncrypted(); The field is a String with possible values "f" or "t". Of convenience reasons I have added a parallell method operating on boolean. My database is designed with a CHAR(1) for booleans. (All this because the dam... RDBMS standard doesn't advice a consistent boolean data type, a really big blunder from time back in System R. OT ok, but I got it out.) When Hibernate parses my instantiated pojo, a Boolean instance is generated. But it's "repository" is prepared with a StringType as a consequence of my XML configuration file. During the course, the method nullSafeSet of class NullableType is called with the value parameter Boolean. Eventually the "public abstract String toString(Object value) throws HibernateException;" method is called for StringType, which is implemented with a simple typecast. Exception received. Whether this behavior is ok or not is one discussion. But there's a second problem to it also: When the exception is received, NullableType tries to log the event: ... catch ( RuntimeException re ) { log().info( "could not bind value '" + nullSafeToString( value ) + "' to parameter: " + index + "; " + re.getMessage() ); throw re; } ... And the same shit happens again. So the developer does not receive the actual exception, but the exception received from the logging statement. A strong golden rule of thumb: A logging statement should never ever throw. This is what I would call a bug in Hibernate. Setting the log level to ERROR will of course not solve the problem, because the string paramater is evaluated before the log statement is ever reached. A variant of this issue is described under: "HHH-2034" -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2456) Memory leak in BasicLazyInitializer

by Julien Kirch (JIRA)

Memory leak in BasicLazyInitializer ----------------------------------- Key: HHH-2456 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2456 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: Hibernate 3.2.2, cglib 2.1.3, jdk 1.4.2, weblogic 8.1 Reporter: Julien Kirch Priority: Blocker Attachments: graph_2.png While profiling our application because of OutOfMemory, I noticed a big memory leak that seems to come from hibernate: After some calls a CGLIBLazyInitializer containing a a SessionImpl is referenced in a threadlocal so it is never GCed even if the session is closed and the calling flow is over Forum thread http://forum.hibernate.org/viewtopic.php?t=968853 seems to deal with the same issue I attached a picture of the profiling information -- 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, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (EJB-251) Incorrect SQL emitted for EJB query involving COUNT()

by Manuel Mall (JIRA)

Incorrect SQL emitted for EJB query involving COUNT() ----------------------------------------------------- Key: EJB-251 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-251 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.ga Environment: Hibernate 3.2 / MySQL 4.1.xx Reporter: Manuel Mall If you have an entity with a composite id and query it like: select count(e) from Entity e the emitted SQL looks like SELECT COUNT(e.id1, e.id2) FROM Entity However, this is at least according to MySQL invalid SQL as the COUNT function can have only one argument. -- 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, 7 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2025) Remove log from LazyInitializationException constructor

by Russell Healy (JIRA)

Remove log from LazyInitializationException constructor ------------------------------------------------------- Key: HHH-2025 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2025 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.1 Environment: Any Reporter: Russell Healy Remove log from LazyInitializationException constructor. The motivation is to enable recovery from a LazyInitializationException using around advice without issuing a logging an error. See: http://www.jroller.com/page/cenkcivici?entry=reattaching_lazy_objects_to_... This has been asked for before [HB-1363], but is worth reconsidering. -- 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, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2010) getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected.

by Lari Hotari (JIRA)

getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected. --------------------------------------------------------------------------------------- Key: HHH-2010 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2010 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3, 3.2.0.cr3 Environment: 3.1.3, DB2 Reporter: Lari Hotari The correct getForUpdateString for DB2 should be "for update with rr" see: http://opensource.atlassian.com/projects/hibernate/browse/HB-1032 DB2 will release all locks created in a result set if the isolation level is lower than TRANSACTION_SERIALIZABLE (RR in DB2). Locks and concurrency control in DB2: http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.do... " The duration of row locking varies with the isolation level being used: * UR scans: No row locks are held unless row data is changing. * CS scans: Row locks are only held while the cursor is positioned on the row. * RS scans: Only qualifying row locks are held for the duration of the transaction. * RR scans: All row locks are held for the duration of the transaction. " -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2116) CLONE -explicit and implicit query with enabled filter gives different results

by Armin Haaf (JIRA)

CLONE -explicit and implicit query with enabled filter gives different results ------------------------------------------------------------------------------ Key: HHH-2116 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2116 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: hibernate 3.2.0.cr2, hibernate annotations 3.2.0.cr1 Reporter: Armin Haaf we are playing around with filters and found a inconsistent behaviour in using a filter in an explicit vs. implicit join. In explicit join a filter is not active, but in an implicit join it is active. Please look at the attachment -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2104) Infinite recursion in org.hibernate.cfg.Configuration.setListener(String, Object)

by Daniel Beer (JIRA)

Infinite recursion in org.hibernate.cfg.Configuration.setListener(String, Object) --------------------------------------------------------------------------------- Key: HHH-2104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2104 Project: Hibernate3 Type: Bug Components: core Versions: 3.1 rc 1 Environment: Hibernate 3.1, but also newer versions contain this bug. Reporter: Daniel Beer When method org.hibernate.cfg.Configuration.setListener(String, Object) is called with second argument set to <null> (in order to remove all listeners of that type) an infinite recursion occurs. Cause: There is a check against null in this method which invokes a wrong method (its a simple typos): if ( listener == null ) { setListener( type, null ); } Instead the method "setListeners(String, Object[])" should be invoked (notice the trailing "s" in the methods name). -- 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, 7 months

2
1
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 April 2007