September 2009 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-4121) DB2 Projection with paging and ordering generates illegal SQL. sqlerror -206

by Nick Wiedenbrück (JIRA)

DB2 Projection with paging and ordering generates illegal SQL. sqlerror -206 ---------------------------------------------------------------------------- Key: HHH-4121 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4121 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.6 Reporter: Nick Wiedenbrück We're using DB2 8.1 and we have a projection query with paging and sorting. The generated SQL looks like this: select * from ( select rownumber() over(order by y5_ asc) as rownumber_, [...] , this_.beginn as y5_, [...] from [...] order by y5_ asc ) as temp_ where rownumber_ <= ? This results in an error, because the query uses the alias in the over() part. If instead this_.beginn would be used it would possibly work. -- 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
1
0 / 0

[Hibernate-JIRA] Created: (ANN-833) Integrate new long string and binary property types in core with annotations

by Gail Badner (JIRA)

Integrate new long string and binary property types in core with annotations ------------------------------------------------------------------------------ Key: ANN-833 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-833 Project: Hibernate Annotations Issue Type: Improvement Reporter: Gail Badner Assignee: Emmanuel Bernard Fix For: 3.5 The following types have been added to core by HHH-3892: - ImageType (image) - MaterializedBlobType (materialized_clob) - MaterializedClobType (materialized_blob) Annotations has its own version of some (or all?) of these types. Annotations should start using these new types instead. -- 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

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4105) SessionFactory mispells method to obtain fetch profile definition

by Paul Benedict (JIRA)

SessionFactory mispells method to obtain fetch profile definition ----------------------------------------------------------------- Key: HHH-4105 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4105 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Reporter: Paul Benedict Line 255: containsFetchProfileDefition Definition is mispelled. -- 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

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3849) Disable lock striping in JBoss Cache configs

by Brian Stansberry (JIRA)

Disable lock striping in JBoss Cache configs -------------------------------------------- Key: HHH-3849 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3849 Project: Hibernate Core Issue Type: Task Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 JBC's MVCC lock striping leads to irresolvable lock conflicts; need to disable it once at least JBC 3.1.0 is integrated. (3.1.0 is the first version that includes the configuration property to disable it.) See http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218836#4218836 for more details. -- 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

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4435) DataVersionAdapter.newerThan incorrect when comparing to self

by Brian Stansberry (JIRA)

DataVersionAdapter.newerThan incorrect when comparing to self ------------------------------------------------------------- Key: HHH-4435 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4435 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0.Beta-1, 3.3.2 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 On 09/10/2009 05:49 PM, Dennis Reed wrote: > Should implementations of org.jboss.cache.optimistic.DataVersion ever > return true for A.newerThan( A ) ? > > I'm guessing not, but the EJB3 entity bean implementation in EAP 4.2/4.3 > does (org.jboss.ejb3.entity.OptimisticJBCCache.DataVersionAdapter). > This seems to be the cause of a DataVersioningException when hibernate > tries to remove a node from the cache. That class is in JBoss AS 4.x, but the org.hibernate.cache.jbc2.util.DataVersionAdapter class has the same problem. I suspect the infinispan version of same does as well, as it was adapted from the JBC version. -- 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
2
0 / 0

[Hibernate-JIRA] Created: (ANN-593) Ability for an @NamedQuery on a @MappedSuperclass to be copied up to the subclass

by John Newman (JIRA)

Ability for an @NamedQuery on a @MappedSuperclass to be copied up to the subclass --------------------------------------------------------------------------------- Key: ANN-593 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-593 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.2.1 Environment: INFO Version:15 - Hibernate Annotations 3.2.1.GA 09:15:01,755 INFO Environment:500 - Hibernate 3.2.1 INFO SettingsFactory:81 - RDBMS: Microsoft SQL Server, version: 08.00.0760 09:15:06,114 INFO SettingsFactory:82 - JDBC driver: jTDS Type 4 JDBC Driver for MS SQL Server and Sybase, version: 1.2 09:15:06,255 INFO Dialect:151 - Using dialect: org.hibernate.dialect.SQLServerDialect Reporter: John Newman If I use a @MappedSuperclass (which is a very useful annotation btw) I have to manually copy any queries I want with taht class up to all subclasses. The binder should check any mapped superclasses and pull those named queries up. i.e. /** * Base User class that different projects user classes derive from. * Hibernate annotations doesn't pick up that query, so you have to copy it up to your subclass */ @MappedSuperclass @NamedQueries({ @NamedQuery(name="User.findByLoginName", query="FROM User WHERE loginName = ?") // this is useless down here, i just put it here for reference }) public class BaseUser<PK extends Serializable> extends IdEntity<PK> { private static final long serialVersionUID = -4443522925041212381L; protected String loginName; @Column(unique=true) public String getLoginName() { return this.loginName; } public void setLoginName(String loginName) { this.loginName = loginName; } } /** * Custom user class for a certain application */ @Entity @Table(name="tbl_user") @GenericGenerator(name=IdGen.NAME, strategy=IdGen.AUTO) @NamedQueries({ @NamedQuery(name="User.findByLoginName", query="FROM User WHERE loginName = ?") // had to copy this up from the base class }) public class User extends BaseUser<Short> { private static final long serialVersionUID = -6199544722824321999L; private String firstName; ... } so in short it would be nice if the scanner would check for that and bind any named queries up to the subclass -- 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

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3000) Allow a TypeDef to be associated with a class

by Darren Bell (JIRA)

Allow a TypeDef to be associated with a class --------------------------------------------- Key: HHH-3000 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3000 Project: Hibernate3 Issue Type: Improvement Reporter: Darren Bell This would allow you to just define it once and not have to worry about adding extra details to the mapping file or by annotating a field. For instance: @TypeDef( name="internalHeaderType", typeClass=com.dolby.mapics.GenericEnumUserType.class, targetClass=com.dolby.mapics.InternalHeaderType, parameters= { @Parameter(name="enumClass", value="com.dolby.mapics.InternalHeaderType"), @Parameter(name="identifierMethod", value="toString"), @Parameter(name="valueOfMethod", value="fromString") }) by adding the targetClass attribute would enable this. -- 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

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2326) NullPointerException from merge on composite id

by Greg Adams (JIRA)

NullPointerException from merge on composite id ----------------------------------------------- Key: HHH-2326 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2326 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1ga, tested against Oracle 10g and Derby Reporter: Greg Adams Priority: Critical Attachments: HibernateMergeBug.zip Merge is throwing an NPE from the bowels of Hibernate when I have a class mapped with a composite ID. Stacktrace: [junit] java.lang.NullPointerException [junit] at org.hibernate.type.AbstractType.getHashCode(AbstractType.java:112) [junit] at org.hibernate.type.AbstractType.getHashCode(AbstractType.java:120) [junit] at org.hibernate.type.EntityType.getHashCode(EntityType.java:279) [junit] at org.hibernate.type.ComponentType.getHashCode(ComponentType.java:189) [junit] at org.hibernate.engine.EntityKey.generateHashCode(EntityKey.java:104) [junit] at org.hibernate.engine.EntityKey.<init>(EntityKey.java:48) [junit] at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:100) [junit] at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:687) [junit] at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:669) [junit] at org.hibernate.engine.CascadingAction$6.cascade(CascadingAction.java:245) [junit] at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:268) [junit] at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:216) [junit] at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) [junit] at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:296) [junit] at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:242) [junit] at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:219) [junit] at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:169) [junit] at org.hibernate.engine.Cascade.cascade(Cascade.java:130) [junit] at org.hibernate.event.def.AbstractSaveEventListener.cascadeAfterSave(AbstractSaveEventListener.java:437) [junit] at org.hibernate.event.def.DefaultMergeEventListener.entityIsTransient(DefaultMergeEventListener.java:194) [junit] at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:123) [junit] at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:53) [junit] at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:677) [junit] at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:661) [junit] at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:665) [junit] at com.foo.test.HibernateTest.doMerge(Unknown Source) [junit] at com.foo.test.HibernateTest.testInsert(Unknown Source) [junit] at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) [junit] at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) [junit] at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) [junit] at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) [junit] at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) [junit] at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:71) [junit] at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) [junit] at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) [junit] at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) [junit] at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) [junit] at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:32) I've attached a zipped-up project that reproduces the error. Just extract and run ant. -- 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

11
13
0 / 0

[Hibernate-JIRA] Created: (HV-242) Cache ConstraintValidator instances per ValidatorFactory and not per ConstraintTree

by Emmanuel Bernard (JIRA)

Cache ConstraintValidator instances per ValidatorFactory and not per ConstraintTree ----------------------------------------------------------------------------------- Key: HV-242 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-242 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.0.0.GA Reporter: Emmanuel Bernard Priority: Minor Fix For: 4.1.0 Evaluate the possibility of caching initialized ConstraintValidator implementations at the ValidatorFactory level instead of creating and initializing them for each ConstraintTree (ie each constraint evaluation. It should be uniquely identified by: - the constraint declaration is belongs to (as it is initialized for a specific constraint) - the ConstraintValidatorFactory it belongs to as this is the CV provider Note that by side effect we will be caching the findMatchingValidatorClass results. Since types are the class types, we can cache the ConstraintValidator class expected to be used for a given constraint declaration. If we cache for all ConstraintValidatorFactory, then a concurrent identity based weak hash map has to be used.as CVF instances provided by users could be discarded rapidly. An alternative would be to cache only for the default VF CVF. In that case the map should only be a concurrent hashmap. -- 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

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-244) Cache the type to ConstraintValidator class computation per constraint declaration

by Emmanuel Bernard (JIRA)

Cache the type to ConstraintValidator class computation per constraint declaration ---------------------------------------------------------------------------------- Key: HV-244 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-244 Project: Hibernate Validator Issue Type: Sub-task Components: engine Affects Versions: 4.0.0.GA Reporter: Emmanuel Bernard Fix For: 4.1.0 -- 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

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2009