April 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4787) AuditProperty.isNull() doesn't generate "tab.col is null" SQL clause as expected

by Eric Citaire (JIRA)

AuditProperty.isNull() doesn't generate "tab.col is null" SQL clause as expected -------------------------------------------------------------------------------- Key: HHH-4787 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4787 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.0.GA Environment: Hibernate 3.3.0.GA, Envers 1.2.2, HSQLDB Database Reporter: Eric Citaire Priority: Critical AuditProperty.isNull() generate a SQL condition like this : "tab.col=?" where the bind variable is mapped to a null value. This doesn't work : most database engines will return false in every case. It should use the "is null" test instead : "tab.col is null" http://en.wikipedia.org/wiki/SQL#Null_and_Three-Valued_Logic_.283VL.29 -- 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

14 years, 11 months

3
5
0 / 0

[Hibernate-JIRA] Commented: (HHH-1237) Escaping : with :: in queries

by Fabrice Daugan (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1237?page=c... ] Fabrice Daugan commented on HHH-1237: ------------------------------------- This patch is a very useful to manage MySql variables "@rowid:=0" Considering the few impacted code, this should easy to be integrated. > Escaping : with :: in queries > ----------------------------- > > Key: HHH-1237 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1237 > Project: Hibernate Core > Issue Type: Patch > Components: core > Affects Versions: 3.1 rc3 > Environment: Hibernate 3, Informix 9.4 > Reporter: Steinar Dahl > Priority: Minor > Attachments: ParameterParser.java > > Original Estimate: 10m > Remaining Estimate: 10m > > Since colons in queries in hibernate currenlty are non-escapable I created a patch (see http://forum.hibernate.org/viewtopic.php?p=2275131#2275131) to make it possible to escape the colon with itself. I needed to do this since I'm using Informix with native sql queries where I'm joining tables from two databases together. In informix you do this by specifiying <database-name>:<table-name> and that didn't work in hibernate since hibernate has reserved the colon for named parameters. -- 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

14 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6160) NPE when setting readOnly hint

by David J. M. Karlsen (JIRA)

NPE when setting readOnly hint ------------------------------ Key: HHH-6160 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6160 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.3 Environment: 3.6.3, jpa2, 64 bit IBM JDK, atomikos jta tx mgr Reporter: David J. M. Karlsen I get the following stack trace when executing a Named Query which was defined like this: <lock-mode>READ</lock-mode> <hint name="org.hibernate.readOnly" value="true" /> if I remove the hint it works fine. {noformat} javax.persistence.PersistenceException: error during managed flush at org.hibernate.ejb.AbstractEntityManagerImpl$3.mapManagedFlushFailure(AbstractEntityManagerImpl.java:1072) at org.hibernate.transaction.synchronization.CallbackCoordinator.beforeCompletion(CallbackCoordinator.java:122) at org.hibernate.transaction.synchronization.HibernateSynchronizationImpl.beforeCompletion(HibernateSynchronizationImpl.java:51) at com.atomikos.icatch.jta.Sync2Sync.beforeCompletion(Sync2Sync.java:55) at com.atomikos.icatch.imp.TransactionStateHandler.commit(TransactionStateHandler.java:278) at com.atomikos.icatch.imp.CompositeTransactionImp.doCommit(CompositeTransactionImp.java:319) at com.atomikos.icatch.imp.CompositeTerminatorImp.commit(CompositeTerminatorImp.java:79) at com.atomikos.icatch.jta.TransactionImp.commit(TransactionImp.java:236) at com.atomikos.icatch.jta.TransactionManagerImp.commit(TransactionManagerImp.java:498) at com.atomikos.icatch.jta.UserTransactionImp.commit(UserTransactionImp.java:129) at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1009) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:754) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:723) at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:393) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.aspectj.AspectJAfterThrowingAdvice.invoke(AspectJAfterThrowingAdvice.java:55) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.framework.adapter.AfterReturningAdviceInterceptor.invoke(AfterReturningAdviceInterceptor.java:50) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.aop.interceptor.AbstractTraceInterceptor.invoke(AbstractTraceInterceptor.java:113) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at net.bull.javamelody.MonitoringSpringInterceptor.invoke(MonitoringSpringInterceptor.java:73) at com.edb.finance.common.spring.aop.monitoring.ExtendedMonitoringSpringInterceptor.invoke(ExtendedMonitoringSpringInterceptor.java:107) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161) at org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:67) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202) at $Proxy157.create(Unknown Source) at com.edb.payment.pays.ws.service.payment.initiate.PaymentInitiateCreateService.handleInternal(PaymentInitiateCreateService.java:45) at com.edb.payment.pays.ws.service.payment.initiate.PaymentInitiateCreateService.handleInternal(PaymentInitiateCreateService.java:12) at com.edb.payment.pays.ws.service.AbstractService.handle(AbstractService.java:96) at com.edb.payment.pays.ws.service.payment.initiate.PaymentInitiateCreateService.pAYSPaymentInitiateCreate_V1_0(PaymentInitiateCreateService.java:27) at sun.reflect.GeneratedMethodAccessor246.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) {noformat} -- 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

14 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HV-466) Avoid repeated validation of constraints in certain type hierarchies

by Gunnar Morling (JIRA)

Avoid repeated validation of constraints in certain type hierarchies -------------------------------------------------------------------- Key: HV-466 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-466 Project: Hibernate Validator Issue Type: Bug Components: engine Reporter: Gunnar Morling Priority: Minor Fix For: 4.x Let there be the following type hierarchy where the same interface is implemented by two types in an inheritance hierarchy: {code:java} public interface A { @NotNull String getA(); } public class B implements A { public String getA() { return null; } } public class C extends B implements A { } {code} When validating an instance of {{C}} the {{@NotNull}} constraint on {{A#getA()}} is evaluated twice when traversing the type hierarchy of {{C}} in {{ValidatorImpl}}. This seems to be against the BV spec. which says in chapter 3.5: {quote} Note that this [algorithm] implies that a given validation constraint will not be processed more than once per validation. {quote} -- 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

14 years, 11 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HV-442) Make clear in the documentation, which types are supported for built-in constraints

by Gunnar Morling (JIRA)

Make clear in the documentation, which types are supported for built-in constraints ----------------------------------------------------------------------------------- Key: HV-442 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-442 Project: Hibernate Validator Issue Type: Bug Components: documentation Affects Versions: 4.1.0.Final Reporter: Gunnar Morling Fix For: 4.2.0.CR1 Hibernate Validator supports the standard constraints defined in the Bean Validation AP at more types than required by the specification. E.g. @Min/@Max are supported for Strings, which is beyond what's defined in the spec. We should make clear in the documentation (http://docs.jboss.org/hibernate/validator/4.1/reference/en-US/html/valida...) which types are supported by HV in addition to the BV specification (for @Past/@Future we already do describe this for the Joda types for example). Furthermore the annotation processor documentation says (reference guide and web site): > Have you ever caught yourself by unintentionally doing things like > annotating Strings with @Min to specify a minimum length (instead of using @Size) > ...? > Then the Hibernate Validator Annotation Processor is the right thing for you. This example is misleading, as the AP won't mark this situation as an erronous (the described misunderstanding, that @Min would refer to the String length can still happen, though). -- 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

14 years, 11 months

2
14
0 / 0

[Hibernate-JIRA] Created: (HHH-6157) Column under a duplicate alias in union-subclass filtered from select statement

by Diego del Río (JIRA)

Column under a duplicate alias in union-subclass filtered from select statement ------------------------------------------------------------------------------- Key: HHH-6157 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6157 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.1 Environment: Hibernate Core 3.6.1.Final Database -> name : HSQL Database Engine version : 1.8.0 major : 1 minor : 8 Driver -> name : HSQL Database Engine Driver version : 1.8.0 major : 1 minor : 8 Reporter: Diego del Río Attachments: test_case.zip I think there is a bug in the process of column alias generation. Given this mapping {code:xml} <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD//EN" "http://www.hibernate.org/dtd/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="org.headlesspigs.domainmodel"> <class name="Invoice" abstract="true"> <id name="id" column="ID" type="long" unsaved-value="0"> <generator class="hilo" /> </id> <property name="name" type="string" column="DS_NAME" /> <union-subclass name="SpecificInvoice" table="TEST_SPECIFIC">  <property name="sameNameAsInvoice" type="string" column="DS_NAME" insert="false" update="false" /> <property name="number" column="DS_NUMBER" type="string" /> <property name="code" column="DS_CODE" type="string" /> </union-subclass> </class> </hibernate-mapping> {code} During the process of alias generation, the column {{DS_CODE}} gets the same alias as the column {{DS_NAME}} from {{SpecificInvoice}}. Later on, when the {{UnionSubclassEntityPersister}} builds the _select_ part of the SQL statement in the method {{propertySelectFragment()}}, {{DS_CODE}} is filtered out from the select string in the method {{SelectFragment.toFragmentString()}}. When the entity is being loaded, the entity loader uses the wrong alias for the {{DS_CODE}} column and instead obtains the value of the column {{DS_NAME}}, leading to an {{SpecificInvoice}} instance with the wrong value for the property _code_. If, instead, the property _code_ had a different type, e.g. {{many-to-one}}, that would potentially lead to an {{ObjectNotFoundException}}, because the identifier used to load the associated entity would be wrong. A test case (along with the mapping file and domain classes) is attached, that shows the entity {{SpecificInvoice}} being loaded with its property _code_ with the wrong value. -- 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

14 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6117) Figure out best way to handle SessionFactoryObjectFactory dealing with JNDI

by Steve Ebersole (JIRA)

Figure out best way to handle SessionFactoryObjectFactory dealing with JNDI --------------------------------------------------------------------------- Key: HHH-6117 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6117 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 Currently {{SessionfactoryObjectFactory}} uses {{JndiHelper}} directly. We really need this using the general notion of {{JndiService}}. The difficulty is the contextual/static split natures. -- 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

14 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6155) Migrate o.h.impl package to o.h.internal

by Steve Ebersole (JIRA)

Migrate o.h.impl package to o.h.internal ---------------------------------------- Key: HHH-6155 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6155 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha3 -- 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

14 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-1907) offload metadata information from ComponentType to SessionFactory

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907?page=c... ] Steve Ebersole updated HHH-1907: -------------------------------- Fix Version/s: (was: 4.0.0.Alpha3) 4.1.0 > offload metadata information from ComponentType to SessionFactory > ----------------------------------------------------------------- > > Key: HHH-1907 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 4.1.0 > > > Specifically, we need to move all the code directly dealing with property-access, instantiation, etc out of here. So where do we move it? Well, EntityType for example moves this stuff off to the persisters; the type then just looks up the persister when needed. Not sure we actually need a persister per-se for handling components; perhaps just ComponentMetamodel is enough... > Why is this important? Well the way ComponentType is currently structured leads to the need for certain configuration properties to be classloader scoped (static on Environment) instead of SessionFactory scoped. This is painful for two in particular: 1) whether to use reflection optimization and 2) bytecode provider. > Also, this change should allow us to cleanup how property accessors are built > Long term it would facilitate the ability to have hierarchies of components as well as loading components in a 2-phase-load paradigm like entities and collections. -- 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

14 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2579) scope bytecode provider selection to session factory

by Steve Ebersole (JIRA)

scope bytecode provider selection to session factory ---------------------------------------------------- Key: HHH-2579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2579 Project: Hibernate3 Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: cfg-rework currently this is one of those "static" config params (classloader wide). -- 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

14 years, 11 months

1
5
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 2011