March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Closed: (HHH-1146) latest cvs(11/10/05) hibernate3 issue with classic query

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1146?page=c... ] Steve Ebersole closed HHH-1146. ------------------------------- Closing stale resolved issues > latest cvs(11/10/05) hibernate3 issue with classic query > --------------------------------------------------------- > > Key: HHH-1146 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1146 > Project: Hibernate Core > Issue Type: Bug > Environment: latest CVS from date 11/10/05 > Reporter: user1 > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.1 rc3 > > > I just took latest cvs hibernate3. I am using classic query - and the queries that used to work, doesn't work with this latest. It gives an error saying : > java.lang.UnsupportedOperationException: select clause aliases ar > e not supported by classic parser > at org.hibernate.hql.classic.QueryTranslatorImpl.getReturnAliases(QueryTranslatorImpl.java:230) > at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:95) > at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:52) > at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:71) > at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:108) > at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:88) > please, can this be fixed? I need to use the latest cvs due to some bugs that got fixed and I need to implement this newly build hibernate3.jar -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1027) session.lock() with UPGRADE_NOWAIT no longer works with Oracle9

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1027?page=c... ] Steve Ebersole closed HHH-1027. ------------------------------- Closing stale resolved issues > session.lock() with UPGRADE_NOWAIT no longer works with Oracle9 > --------------------------------------------------------------- > > Key: HHH-1027 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1027 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc 1 > Environment: Hibernate 3.1 beta 3 > Oracle 9 > Reporter: Achim Lörke > Assignee: Steve Ebersole > Priority: Blocker > > With fix HHH-924 the SQLStateConverter replaced the version from Oracle9Dialect. This generic converter doesn't handle the error codes from Oracle when UGRADE_NOWAIT is used and the row is already locked, so instead of getting a LockAcquisitionException a GenericSQLException is thrown. (org.hibernate.exception.ErrorCodeConverter which handled this kind of SQL errors was removed, too). > This breaks a lot of code which relies on locking with Oracle. -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1017) Mapping Jar not closed after read

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1017?page=c... ] Steve Ebersole closed HHH-1017. ------------------------------- Closing stale resolved issues > Mapping Jar not closed after read > --------------------------------- > > Key: HHH-1017 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1017 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 beta 2 > Reporter: Gerald Glocker > Priority: Minor > > After reading the mapping jar the file should be closed (Configuration.addJar) . > Leaving the file open prevents applications to be undeployed (e.g. in tomcat). -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1546) generated version properties fail with multiple actions per flush

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1546?page=c... ] Steve Ebersole closed HHH-1546. ------------------------------- Closing stale resolved issues > generated version properties fail with multiple actions per flush > ----------------------------------------------------------------- > > Key: HHH-1546 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1546 > Project: Hibernate Core > Issue Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.0.alpha2, 3.1.3 > > > An entity with a version property that is defined as generated will cause bogus optimistic lock failures if the given entity has multiple queued actions for a given flush cycle. The cause is that the actions are constructed before any of the DML has been executed and cache the "previousVersion" to use for optimistic locking based on the entity's current state. -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1127) HQL's special use of the "id" property name interferes with user Object models

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1127?page=c... ] Steve Ebersole closed HHH-1127. ------------------------------- Closing stale resolved issues > HQL's special use of the "id" property name interferes with user Object models > ------------------------------------------------------------------------------ > > Key: HHH-1127 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1127 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Environment: Hibernate HQL in all of its versions up to the recent version 3.1 > Reporter: Gunther Schadow > Original Estimate: 8h > Remaining Estimate: 8h > > When a user decides to use the name "id" as the name of a property, HQL queries break with unspecific exceptions, because HQL assumes "id" as reserved for the Hibernate id attribute defined in the hbm file using the <id .../> tag. This is bad design in our view, because it puts an unnecessary constraint and interference with the otherwise transparent "object persistence for idiomatic Java." > For example, a mapping file may contain: > <class name="MyObject"> > <id name="internalId" ... /> > <property name="id" .../> > <property name="foo" .../> > </class> > now I like to make an HQL query > from MyObject where id='123' > and this would fail because 'id' in HQL means the 'internalId' property not the property called 'id'. > I could hack org.hibernate.persister.entity.EntityPersister, changing line > public static final String ENTITY_ID = "id"; > to > public static final String ENTITY_ID = "hid"; > But that of course is breaking it for anyone who uses "hid" as a normal property name. > I think the flaw here is that HQL should use the hbm metadata to take the attribute designated as by > the class/id/@name attribute in the mapping file rather than using this static constant "id" literal. > The following classes use the ENTITY_ID constant: > hql/ast/tree/DotNode.java > hql/ast/tree/FromElement.java > hql/ast/tree/FromElementType.java > hql/classic/PathExpressionParser.java > persister/entity/AbstractEntityPersister.java > persister/entity/AbstractPropertyMapping.java > persister/entity/EntityPersister.java > and most of the work would be in PathExpressionParser, for someone who knows this it should > not take more than a day to fix. > The problem is that it would break backward compatibility with existing HQL queries. But there is really no alternative than to make the change, because either you keep it a perpetual problem for new users or you make it a short term problem for old users. One might consider using some special symbol, such as "@id" to stand as an alias for the actual name of the id property. That would make conversion really easy. -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1028) After upgrading to 3.1-rc1 from beta3 I am getting the following exception.

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1028?page=c... ] Steve Ebersole closed HHH-1028. ------------------------------- Closing stale resolved issues > After upgrading to 3.1-rc1 from beta3 I am getting the following exception. > --------------------------------------------------------------------------- > > Key: HHH-1028 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1028 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc 1 > Reporter: Keith Garry Boyce > Assignee: Steve Ebersole > Priority: Critical > > After upgrading to 3.1-rc1 from beta3 I am getting the following exception. I don't have a test case but I am merely reporting and issue I saw with upgrade. When reverting to beta3 jar problem goes away. > 2005-10-08 19:12:58,426 INFO [Thread-73] org.springframework.orm.hibernate3.HibernateTransactionManager - Could not access JDBC connection of Hibernate session > org.hibernate.SessionException: Session is currently disconnected > at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:134) > at org.hibernate.jdbc.JDBCContext.userConnection(JDBCContext.java:125) > at org.hibernate.impl.SessionImpl.connection(SessionImpl.java:366) > at org.springframework.orm.hibernate3.HibernateTransactionManager.doCleanu > pAfterCompletion(HibernateTransactionManager.java:548) > at org.springframework.transaction.support.AbstractPlatformTransactionMana > ger.cleanupAfterCompletion(AbstractPlatformTransactionManager.java:645) > at org.springframework.transaction.support.AbstractPlatformTransactionMana > ger.commit(AbstractPlatformTransactionManager.java:470) > at org.springframework.transaction.interceptor.TransactionAspectSupport.do > CommitTransactionAfterReturning(TransactionAspectSupport.java:258) > at org.springframework.transaction.interceptor.TransactionInterceptor.invo > ke(TransactionInterceptor.java:67) > at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Re > flectiveMethodInvocation.java:144) > at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicA > opProxy.java:174) -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-112) AST QueryTranslatorImpl does not check set compiled=true

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-112?page=co... ] Steve Ebersole closed HHH-112. ------------------------------ Closing stale resolved issues > AST QueryTranslatorImpl does not check set compiled=true > -------------------------------------------------------- > > Key: HHH-112 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-112 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0 beta 2 > Environment: Hibernate 3.0 beta2 (source from download, not cvs) > Reporter: Jonas Van Poucke > Assignee: Joshua Davis > Priority: Trivial > > Looking at the code, I found the attribute > "private boolean compiled;" > never set to true in org.hibernate.hql.ast.QueryTranslatorImpl > Might be a speed improvement? > Moreover, the synchronization is somewhat weird: there are two public compile() methods and only one of them is synchronized. Forgot to sync one? -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1541) incorrect transaction status reported

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1541?page=c... ] Steve Ebersole closed HHH-1541. ------------------------------- Closing stale resolved issues > incorrect transaction status reported > ------------------------------------- > > Key: HHH-1541 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1541 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1.2 > Environment: Hibernate 3.1.2, MySQL 5 (INNODB tables), MySQL 5 JDBC, SuSe 10.0 linux > Reporter: Peter Stein > Assignee: Steve Ebersole > Attachments: 1590595114-2823.zip > > > Running the GenerateDeadlock example from chapter 9 of "Pro Hibernate 3" (www.apress.com) reveals that transaction status is not reported correctly. At no time is a HibernateException caught (to indicate deadlock) nor do the Transaction methods wasRolledBack() and wasCommitted() return correct values. wasRolledBack() is never true. Worse yet, wasCommitted() is actually true for transactions that were rolled back! -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-764) XML mapping

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-764?page=co... ] Steve Ebersole closed HHH-764. ------------------------------ Closing stale resolved issues > XML mapping > ----------- > > Key: HHH-764 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-764 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.0.5 > Environment: 3.0.5,windows > Reporter: Francois-xavier.brun > Assignee: Steve Ebersole > Fix For: 3.1 rc3 > > Attachments: hhh764.jar > > Original Estimate: 8h > Remaining Estimate: 8h > > The map-key index is not mapped on the XML document for a collection of composite-elements -- 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

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-986) Need to check Thread.currentThread().getContextClassLoader() in ConfigHelper

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-986?page=co... ] Steve Ebersole closed HHH-986. ------------------------------ Closing stale resolved issues > Need to check Thread.currentThread().getContextClassLoader() in ConfigHelper > ---------------------------------------------------------------------------- > > Key: HHH-986 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-986 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1 beta 2 > Environment: Hibernate 3.1 b3, maven > Reporter: Alexander Borovsky > Assignee: Gavin King > Priority: Critical > Fix For: 3.1 rc 1 > > > Thread.currentThread().getContextClassLoader() is null when I generate schema from maven, And I get NullPointerException, in configuration initialization -- 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

1
0
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 March 2011