December 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6881) identity strategy AUTO uses SequenceStyleGenerator on mssql

by andreas bleicher (JIRA)

identity strategy AUTO uses SequenceStyleGenerator on mssql ----------------------------------------------------------- Key: HHH-6881 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6881 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR2 Environment: Hibernate 4.0.0.CR2, JBoss 7.0.2, MSSQL2008, JTDS-1.2.5 Reporter: andreas bleicher Priority: Blocker we are using identity generation with default strategy (GenerationType.AUTO) to support different DBMS (mssql, oracle, mysql) our Id annotations: {Code} @Id @GeneratedValue public long getId() { return id; } {Code} since upgrading to jboss7/hibernate4 we get the following error on mssql when persisting a new entity: 14:33:10,373 ERROR [org.hibernate.id.enhanced.TableStructure] (http--127.0.0.1-8080-3) could not read a hi value: java.sql.SQLException: invalid object name 'hibernate_sequence'. the reason is that instead of the IdentityGenerator the SequenceStyleGenerator is used although we are using the correct MSSQLServerDialect and it returns supportsIdentityColumns() = true. The SequenceStyleGenerator tries to find the 'hibernate_sequence' table which does not exist workaround for mssql by changing code to: {Code} @Id @GeneratedValue(strategy=GenerationType.IDENTITY) public long getId() { return id; } {Code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5684) Change Javassist usage to not use javassist.util.proxy.ProxyFactory

by Steve Ebersole (JIRA)

Change Javassist usage to not use javassist.util.proxy.ProxyFactory ------------------------------------------------------------------- Key: HHH-5684 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5684 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Fix For: 4.0.0.Alpha2 javassist.util.proxy.ProxyFactory maintains a cache of proxy classes generated. Apparently it does this based on a static variable. First and foremost, this cache is completely unnecessary given how Hibernate creates and uses these proxy classes. Second there is some conjecture that this might possibly contribute to permgen leaks. -- 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

1
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5688) Migrate BytecodeProvider to be a Service

by Steve Ebersole (JIRA)

Migrate BytecodeProvider to be a Service ---------------------------------------- Key: HHH-5688 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5688 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 This is deeply dependent upon the metamodel redesign completion. -- 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

2
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-638) Limit graph traversal by @ContainedIn to the minimum required path

by Sanne Grinovero (JIRA)

Limit graph traversal by @ContainedIn to the minimum required path ------------------------------------------------------------------ Key: HSEARCH-638 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-638 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.2.1, 3.2.0.Final, 3.1.1.GA, 3.1.0.GA, 3.3.0 Reporter: Sanne Grinovero Unit test available in the source tree since HSEARCH-513 org.hibernate.search.test.embedded.depth.RecursiveGraphTest, see the "FIXME" referring to this issue. It seems that @ContainedIn is now traversing the graph "upwards" towards any related entity it might find, without any limit; this happens to work pretty well in most simple use cases but becomes a performance problem in the more complex scenarios. -- 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

2
10
0 / 0

[Hibernate-JIRA] Created: (HHH-6606) org.hibernate.metamodel.source.annotations.util.EmbeddableHierarchyTest#testEmbeddableHierarchy fails on openjdk

by Strong Liu (JIRA)

org.hibernate.metamodel.source.annotations.util.EmbeddableHierarchyTest#testEmbeddableHierarchy fails on openjdk ---------------------------------------------------------------------------------------------------------------- Key: HHH-6606 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6606 Project: Hibernate Core Issue Type: Bug Components: metamodel Affects Versions: 4.0.0.CR1 Reporter: Strong Liu Assignee: Hardy Ferentschik Fix For: 4.0.0.next Hardy, i'm assigning this to you since you wrote this test :) {code} junit.framework.AssertionFailedError: wrong class expected:<org.hibernate.metamodel.source.annotations.util.EmbeddableHierarchyTest$1A> but was:<org.hibernate.metamodel.source.annotations.util.EmbeddableHierarchyTest$1C> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at org.hibernate.metamodel.source.annotations.util.EmbeddableHierarchyTest.testEmbeddableHierarchy(EmbeddableHierarchyTest.java:72) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:63) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.hibernate.testing.junit4.FailureExpectedHandler.evaluate(FailureExpectedHandler.java:59) at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.hibernate.testing.junit4.BeforeClassCallbackHandler.evaluate(BeforeClassCallbackHandler.java:43) at org.hibernate.testing.junit4.AfterClassCallbackHandler.evaluate(AfterClassCallbackHandler.java:42) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:51) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:63) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:49) at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:75) at $Proxy3.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:86) at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.remote.internal.MethodInvocationUnmarshallingDispatch.dispatch(MethodInvocationUnmarshallingDispatch.java:48) at org.gradle.messaging.dispatch.DiscardOnFailureDispatch.dispatch(DiscardOnFailureDispatch.java:31) at org.gradle.messaging.dispatch.AsyncDispatch.dispatchMessages(AsyncDispatch.java:129) at org.gradle.messaging.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:33) at org.gradle.messaging.dispatch.AsyncDispatch$1.run(AsyncDispatch.java:69) at org.gradle.messaging.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:63) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-6847) HibernateSearch DSL - excludeLimit()

by S M (JIRA)

HibernateSearch DSL - excludeLimit() ------------------------------------ Key: HHH-6847 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6847 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.2 Reporter: S M Priority: Minor As in HibernateCore 3.6.2 (with HibernateSearch 3.3.1) I found the following error: The class ConnectedMultiFieldsRangeQueryBuilder has to implement the method excludeLimit(), in which the border to be excluded is checked. The upper border is excluded correctly, but the lower border needs to be excluded with: rangeContext.setExcludeFrom(true) instead of rangeContext.setExcludeTo(true) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-951) excludeLimit() has no effect on QueryBuilder.range().above() queries

by Marko Lukša (JIRA)

excludeLimit() has no effect on QueryBuilder.range().above() queries -------------------------------------------------------------------- Key: HSEARCH-951 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-951 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 4.0.0.CR1, 3.4.1.Final Reporter: Marko Lukša Priority: Trivial When executing the following code, the {{excludeLimit()}} call has no effect. {code} Query query = queryBuilder .range() .onField("letter") .ignoreFieldBridge() .ignoreAnalyzer() .above("b").excludeLimit() .createQuery(); {code} It's caused by a minor bug in {{ConnectedMultiFieldsRangeQueryBuilder.excludeLimit()}}: {code} public RangeTerminationExcludable excludeLimit() { if ( rangeContext.getFrom() != null && rangeContext.getTo() != null ) { rangeContext.setExcludeTo( true ); } else if ( rangeContext.getFrom() != null ) { rangeContext.setExcludeTo( true ); <---- should be From, not To } else if ( rangeContext.getTo() != null ) { rangeContext.setExcludeTo( true ); } else { throw new AssertionFailure( "Both from and to clause of a range query are null" ); } return this; } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
5
0 / 0

[Hibernate-JIRA] Deleted: (HHH-6893) Apply patch provided by Harald

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6893?page=c... ] Steve Ebersole deleted HHH-6893: -------------------------------- > Apply patch provided by Harald > ------------------------------ > > Key: HHH-6893 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6893 > Project: Hibernate Core > Issue Type: Sub-task > Reporter: Dirk Feufel > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6922) The usage of Mysql DATE_SUB function

by anoop kumar (JIRA)

The usage of Mysql DATE_SUB function ------------------------------------ Key: HHH-6922 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6922 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.0 alpha Environment: Hibernate 3.0 in Mysql database Reporter: anoop kumar There is no direct method for implementing the DATE_SUB function using hibernate CreateQuery method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6894) ClassNotFoundException with Atomikos

by Michał Matłoka (JIRA)

ClassNotFoundException with Atomikos ------------------------------------ Key: HHH-6894 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6894 Project: Hibernate Core Issue Type: Bug Affects Versions: 4.0.0.CR7 Environment: Hibernate 4.0.0.CR7, Spring 3.1.0.RELEASE, Atomikos 3.7.0 Reporter: Michał Matłoka I've just tried to change from Hibernate 3.6.8 to 4.0.0.CR7. I've upgraded jar's and changed sessionFactory to org.springframework.orm.hibernate4.LocalSessionFactoryBean. On server startup I get java.lang.ClassNotFoundException: Could not load requested class : com.atomikos.icatch.jta.hibernate3.AtomikosJTATransactionFactory . Only hibernate jar's were changed, all needed atomikos jar's are still available. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2011