July 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (ANN-30) @OnDelete

by Arik Kfir (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-30?page=com... ] Arik Kfir commented on ANN-30: ------------------------------ Actually, @OnDelete for many-to-many associations would be <b>very</b> handy. +1 > @OnDelete > --------- > > Key: ANN-30 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-30 > Project: Hibernate Annotations > Issue Type: Improvement > Components: binder > Affects Versions: 3.1beta3 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Trivial > > @OnDelete(type=OnDeleteType.NOACTION) > OnDeleteType.CASCADE > used on an indexed collection -- 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

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2152) Optimistic lock error although using LockMode.UPGRADE

by Per-Olov Wingren (JIRA)

Optimistic lock error although using LockMode.UPGRADE ----------------------------------------------------- Key: HHH-2152 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2152 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Oracle 10.2, Hibernate 3.1.3 Reporter: Per-Olov Wingren Priority: Critical Attachments: OptLockProblem.zip I have a situation where two threads tries to update the same entity object at the same time. I use the Hibernate managed versioning using a version number but also a pessimistic lock using LockMode.UPGRADE. One thread will lock the object in the database and the other will wait for the transaction of the first thread to commit (or rollback). The first thread updates the object, which also will make its version to be incremented. When the second tread get access to the object after the first is commited, it get an incorrect value of the version attribute. This leads to a StaleObjectStateException when the transaction is commited. The entity object conists of a parent class and a subclass mapped to the database into two tables using <joined-subclass>. If the testcase is modified to update an attribute in the subclass (numberB) instead of in the superclass it works without errors. Is the problem caused by the fact that Hibernate only locks the subclass in the database (for update of classb.oid) and not the superclass? I attache a zip file containing a simple but complete test case that shows the problem. -- 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

17 years, 5 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-39) Support average for Criteria

by Max Ross (JIRA)

Support average for Criteria ---------------------------- Key: HSHARDS-39 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-39 Project: Hibernate Shards Issue Type: New Feature Components: query Affects Versions: 3.0.0.Beta1 Reporter: Max Ross Assignee: Max Ross Fix For: 3.0.0.beta2 Need to support the average projection on Criteria -- 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

17 years, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-4) extend shard locking to criteria and query

by Max Ross (JIRA)

extend shard locking to criteria and query ------------------------------------------ Key: HSHARDS-4 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-4 Project: Hibernate Shards Issue Type: New Feature Components: query Affects Versions: 3.0.0.Beta1 Reporter: Max Ross Assignee: Max Ross Fix For: 3.0.0.beta2 We currently give people the ability to lock the shard used for shard selection, but we should extend this to shard resolution, criteria, and query. The use case is a request that does all of its db work against a single shard. Shards should give the user the ability to perform some operation to determine what shard should be used and then lock in that shard so that all subsequent db access via the ShardedSession only uses that one shard. -- 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

17 years, 5 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2557) NPE in IdentityMap.IdentityKey.equals()

by Anders Wallgren (JIRA)

NPE in IdentityMap.IdentityKey.equals() --------------------------------------- Key: HHH-2557 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2557 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Reporter: Anders Wallgren The equals method in org.hibernate.util.IdentityMap.IdentityKey doesn't handle null objects: {code} java.lang.NullPointerException at org.hibernate.util.IdentityMap$IdentityKey.equals(IdentityMap.java:103) at java.util.HashMap.get(HashMap.java:305) at org.apache.commons.collections.SequencedHashMap.get(SequencedHashMap.java:288) at org.hibernate.util.IdentityMap.get(IdentityMap.java:135) at org.hibernate.engine.StatefulPersistenceContext.getEntry(StatefulPersistenceContext.java:355) at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:54) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:301) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at com.electriccloud.dao.HibernateFlushListener.onFlush(HibernateFlushListener.java:49) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.springframework.orm.hibernate3.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:575) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:651) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:621) at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:311) at com.electriccloud.dao.TransactionAspect.withTransaction(TransactionAspect.java:121) at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:576) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:562) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:60) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:76) at com.electriccloud.operations.ConcurrentRetryAspect.performWithRetry(ConcurrentRetryAspect.java:168) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:576) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:562) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:60) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:76) at com.electriccloud.operations.OperationTimingAspect.logOperationPerformance(OperationTimingAspect.java:110) at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:576) at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:562) at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:60) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:203) at $Proxy97.perform(Unknown Source) at com.electriccloud.operations.OperationInvoker.invoke(OperationInvoker.java:190) at com.electriccloud.operations.OperationCaller.call(OperationCaller.java:126) at com.electriccloud.operations.OperationCaller.call(OperationCaller.java:36) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) at com.electriccloud.util.queue.CommanderThread.run(CommanderThread.java:78) {code} -- 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

17 years, 5 months

4
8
0 / 0

[Hibernate-JIRA] Commented: (HHH-1604) IdentityKey.equals(Object) using == instead of myBean.equals(Object)

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1604?page=c... ] Steve Ebersole commented on HHH-1604: ------------------------------------- I'll give you a little bit to think it through... > IdentityKey.equals(Object) using == instead of myBean.equals(Object) > -------------------------------------------------------------------- > > Key: HHH-1604 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1604 > Project: Hibernate3 > Issue Type: Bug > Components: core > Environment: Hibernate 3.0.1 > Reporter: Joel SCHAAL > > When trying to remove an instance from the cache with session.evict, I am confused to see that an instance is not effectively removed. > After getting in the code I see that IdentityKey uses == and not my overrided equals method in my bean object. > Shouldn't IdentityKey use equals ? It would make more sense, wouldn't it ? Because in the specification of java.util.Map, it is equals that is mentionned, not ==. > Thanks in advance for letting me know if I am wrong and/or if this will be changed. > Joel. > Class concerned : org.hibernate.util.IdentityMap -- 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

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2752) Primary Key generation on Oracle 9.2

by Markus Lehrhuber (JIRA)

Primary Key generation on Oracle 9.2 ------------------------------------ Key: HHH-2752 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2752 Project: Hibernate3 Issue Type: Bug Components: build Affects Versions: 3.2.4.sp1 Environment: Oracle 9.2, Hibernate 3.2.4.sp1, Java 1.4.2 Reporter: Markus Lehrhuber Priority: Blocker As described in http://forum.hibernate.org/viewtopic.php?t=977947 there seems to be a Problem on creating primary keys for Oracle 9.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

17 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1604) IdentityKey.equals(Object) using == instead of myBean.equals(Object)

by Joel SCHAAL (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1604?page=c... ] Joel SCHAAL commented on HHH-1604: ---------------------------------- Please, could I have a reason why the bug has been rejected ? > IdentityKey.equals(Object) using == instead of myBean.equals(Object) > -------------------------------------------------------------------- > > Key: HHH-1604 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1604 > Project: Hibernate3 > Issue Type: Bug > Components: core > Environment: Hibernate 3.0.1 > Reporter: Joel SCHAAL > > When trying to remove an instance from the cache with session.evict, I am confused to see that an instance is not effectively removed. > After getting in the code I see that IdentityKey uses == and not my overrided equals method in my bean object. > Shouldn't IdentityKey use equals ? It would make more sense, wouldn't it ? Because in the specification of java.util.Map, it is equals that is mentionned, not ==. > Thanks in advance for letting me know if I am wrong and/or if this will be changed. > Joel. > Class concerned : org.hibernate.util.IdentityMap -- 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

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2749) Remove reflection based handling of LinkedHashSet and LinkedHashMap

by Steve Ebersole (JIRA)

Remove reflection based handling of LinkedHashSet and LinkedHashMap ------------------------------------------------------------------- Key: HHH-2749 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2749 Project: Hibernate3 Issue Type: Sub-task Reporter: Steve Ebersole Assignee: Steve Ebersole -- 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

17 years, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2748) Replace SequencedHashMap usage with LinkedHashMap

by Steve Ebersole (JIRA)

Replace SequencedHashMap usage with LinkedHashMap ------------------------------------------------- Key: HHH-2748 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2748 Project: Hibernate3 Issue Type: Sub-task Reporter: Steve Ebersole Assignee: Steve Ebersole -- 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

17 years, 5 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007