March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Closed: (HHH-889) Add read-only cache-mode comment in <query and <sql-query

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-889?page=co... ] Steve Ebersole closed HHH-889. ------------------------------ Closing stale resolved issues > Add read-only cache-mode comment in <query and <sql-query > --------------------------------------------------------- > > Key: HHH-889 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-889 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Emmanuel Bernard > Priority: Minor > Fix For: 3.1 rc 1 > > -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1201) Classic parser does not support DML style operations

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1201?page=c... ] Steve Ebersole closed HHH-1201. ------------------------------- Closing stale resolved issues > Classic parser does not support DML style operations > ---------------------------------------------------- > > Key: HHH-1201 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1201 > Project: Hibernate Core > Issue Type: Bug > Environment: CVS HEAD > Reporter: Mathias Bogaert > Priority: Blocker > > Exception in thread "Thread-134" org.springframework.orm.hibernate3.HibernateQueryException: query must begin with SELECT or FROM: delete [delete from UnarchivedSample u where u.CABLE_MODEM_SAMPLE_ID = :CM_ID]; nested exception is org.hibernate.QueryException: query must begin with SELECT or FROM: delete [delete from UnarchivedSample u where u.CABLE_MODEM_SAMPLE_ID = :CM_ID] > org.hibernate.QueryException: query must begin with SELECT or FROM: delete [delete from UnarchivedSample u where u.CABLE_MODEM_SAMPLE_ID = :CM_ID] > at org.hibernate.hql.classic.ClauseParser.token(ClauseParser.java:83) > at org.hibernate.hql.classic.PreprocessingParser.token(PreprocessingParser.java:108) > at org.hibernate.hql.classic.ParserHelper.parse(ParserHelper.java:28) > at org.hibernate.hql.classic.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:178) > at org.hibernate.hql.classic.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:154) > at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:74) > at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:53) > 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) > at nl.nutsmaas.marvin.domain.persistence.hibernate.HibernateCableModemDao.archiveSamples(HibernateCableModemDao.java:195) > Code: > String hqlDelete = "delete from UnarchivedSample u where u.CABLE_MODEM_SAMPLE_ID = :CM_ID"; > int deletedEntities = getSessionFactory().getCurrentSession().createQuery( hqlDelete ) > .setLong( ":CM_ID", cableModem.getId()).executeUpdate(); > log.info("Deleted " + deletedEntities + " unarchived cable modem samples"); -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-896) <bag> doesn't support NOT-NULL

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-896?page=co... ] Steve Ebersole closed HHH-896. ------------------------------ Closing stale resolved issues > <bag> doesn't support NOT-NULL > ------------------------------ > > Key: HHH-896 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-896 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Reporter: leonardo susatyo > > <component > name="checkMessages" > class="xxx.CheckMessages"> > <bag > name="messages" > lazy="false" > cascade="all-delete-orphan"> > <key column="claim_id" not-null="true"/> > <one-to-many class="xxx.CheckMessage"/> > </bag> > </component> > <bag> setting with <key column="" not-null="true"/> is not working. the application thrown error that's also not very helpful > [junit] org.hibernate.MappingException: Unknown entity: xxx.checkMessages -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-982) Autoclosing connections in JTA env. after session.connection() in 3.1.rc1

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-982?page=co... ] Steve Ebersole closed HHH-982. ------------------------------ Closing stale resolved issues > Autoclosing connections in JTA env. after session.connection() in 3.1.rc1 > ------------------------------------------------------------------------- > > Key: HHH-982 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-982 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc 1 > Environment: Hibernate 3.1.rc1 > Hibernate annotations 3.1.rc1 > JOTM 2.0.10 > Reporter: Sergey Vladimirov > > After moving from Hibernate 3.0.5 to 3.1.rc1, this code works wrong: > public void testMultiJTATransactions() throws Exception { > UserTransaction userTransaction = JOTMTransactionFactory > .getUserTransaction(); > for (int i = 0; i < 100; i++) { > userTransaction.begin(); > Session session = sessionFactory.getCurrentSession(); > session.connection(); > userTransaction.commit(); > } > } > In 3.0 all session connections closes after transaction.commit, but not in 3.1 - all connections locked in XA pool: -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1014) id should still be null after unsuccessful saving of a new object - but isn't

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1014?page=c... ] Steve Ebersole closed HHH-1014. ------------------------------- Closing stale resolved issues > id should still be null after unsuccessful saving of a new object - but isn't > ----------------------------------------------------------------------------- > > Key: HHH-1014 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1014 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: postgresql, hibernate wired up via spring, also reproducible with 3.1 beta 3 > Reporter: Thomas Jachmann > Assignee: Steve Ebersole > > I have quite a simple object: Utility. It's property name has to be unique: > <class name="Utility"> > <id name="id"> > <generator class="sequence"/> > </id> > <version name="version"/> > <property name="name" unique="true" not-null="true"/> > <many-to-one name="postalAddress" column="postal_address_id" lazy="false" cascade="all" not-null="true"/> > <many-to-one name="client" class="Client" column="client_id" lazy="false" cascade="all"/> > <property name="phone"/> > <property name="fax"/> > </class> > I think that the other properties/relationships don't matter. > When I save a new Utility that's name already is in the database, I get a ConstraintViolationException. This is expected behaviour. But afterwards, the id of the utility is set. So are those of all related objects (postalAddress and client). As far as I understand it, they should be null indicating that the objects are still not persistet. When I change the name and try to save it again, I get a StaleObjectStateException. This seems to be a bug, since actually, the object isn't in the database because of the constraint violation. > Regards, > Thomas -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1371) MappingException is thrown when the same column is referenced with different case

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1371?page=c... ] Steve Ebersole closed HHH-1371. ------------------------------- Closing stale resolved issues > MappingException is thrown when the same column is referenced with different case > --------------------------------------------------------------------------------- > > Key: HHH-1371 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1371 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1.1 > Environment: Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - Production With the Partitioning, OLAP and Data Mining options > JDBC Driver Version is Oracle JDBC driver 10.2.0.1.0 > Oracle Application Server Containers for J2EE 10g (10.1.2.0.2) (OC4J) > Reporter: Jifeng Liu > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.1.2 > > Attachments: hibernate.cfg.xml, stacktrace.txt > > > I got org.hibernate.MappingException: Same logical column name referenced several times: Marking_Periods.School_Id School_ID School_Id. Please see attached file for full stack trace. My mapping file works for Hibernate 3.1. But it fails after I installed Hibernate 3.1.1 jar file. > The mapping file that causes MappingException is: > <hibernate-mapping> > <class name="com.senior.bll.academic.school.MarkingPeriod" > table="Marking_Periods" rowid="rowid"> > <composite-id> > <key-property name="schoolId" column="School_ID"/> > <key-property name="academicYear" column="Academic_Yr"/> > <key-property name="sortNo" column="Period_Sort_No"/> > </composite-id> > <property name="name" column="Name"/> > <property name="abbrev" column="Abbrev"/> > >  > <property name="termSortNo" column="Term_Sort_No"/> > <many-to-one name="term" cascade="save-update" > fetch="join" insert="false" update="false" > > > <column name="School_Id" /> > <column name="Academic_Yr" /> > <column name="Term_Sort_No" /> > </many-to-one> > > <filter name="schoolId" condition="School_Id=:schoolId"/> > </class> > </hibernate-mapping> -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-853) DML-style HQL queries and associations

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-853?page=co... ] Steve Ebersole closed HHH-853. ------------------------------ Closing stale resolved issues > DML-style HQL queries and associations > -------------------------------------- > > Key: HHH-853 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-853 > Project: Hibernate Core > Issue Type: Bug > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Fix For: 3.1.1 > > > Currently, associations cannot be referenced in the delete/update/insert HSQL statements. -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1284) Named parameter bug

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1284?page=c... ] Steve Ebersole closed HHH-1284. ------------------------------- Closing stale resolved issues > Named parameter bug > ------------------- > > Key: HHH-1284 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1284 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: hibernate 3.0.5 , Oracle > Reporter: Dilip Ranjith > > I tried to excute this query > select a.timeHrs|| ' : ' ||a.timeMins from CreatedTIme a > instead of getting a result like this 8:30 iam getting an exception > org.hibernate.QueryException: Not all named parameters have been set: [] [select a.timeHrs|| ' : ' ||a.timeMins from CreatedTIme a] > at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:115) > at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:102) > at org.hibernate.impl.QueryImpl.list(QueryImpl.java:70) > the string ' : ' is being taken as a named parameter declaration instead of a string -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1373) Document update versioned

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1373?page=c... ] Steve Ebersole closed HHH-1373. ------------------------------- Closing stale resolved issues > Document update versioned > ------------------------- > > Key: HHH-1373 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1373 > Project: Hibernate Core > Issue Type: Task > Components: documentation > Affects Versions: 3.1.1 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.1.2 > > -- 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

13 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1155) why do hibernate session provide optinal method for developers to decide whether cache the object in order to improve the performance of bulk operation

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1155?page=c... ] Steve Ebersole closed HHH-1155. ------------------------------- Closing stale resolved issues > why do hibernate session provide optinal method for developers to decide whether cache the object in order to improve the performance of bulk operation > ----------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-1155 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1155 > Project: Hibernate Core > Issue Type: New Feature > Components: core > Environment: any version > Reporter: Rock Tian > Attachments: sample .txt > > Original Estimate: 8h > Remaining Estimate: 8h > > when we process bulk operation such as save or find,the Session will cache the object,but you will find that it will cosume too much memory and result in "..out of memory".provided we can decide whether to cache the object when use the method,and don'nt cache the object,it will be no problem.if don'nt ,we have to evict object in every while,JVM will become stableless and the speed of operation is slow. -- 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

13 years, 10 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 March 2011