August 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3465) HiRDB Support

by Tomoto Shimizu Washio (JIRA)

HiRDB Support ------------- Key: HHH-3465 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3465 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.5 Environment: 3.2.5 + HiRDB V8 + Type4 JDBC Driver Reporter: Tomoto Shimizu Washio Attachments: hirdbdialect.patch I would like to contribute with a dialect for HiRDB, Hitachi's RDBMS. (For more information, please see http://www.hitachi.co.jp/Prod/comp/soft1/global/prod/hirdb/) I added 4 classes and slightly modified 2 existing classes as shown below. Please look at the documentation at the top of the patch for explanations. org.hibernate.dialect.HiRDBDialect (added) org.hibernate.dialect.UserFuncDeclParser (added) org.hibernate.dialect.DialectFactory (modified) org.hibernate.dialect.function.AnsiTrimEmulationFunction (modified) org.hibernate.dialect.function.AnsiTrimEmulationFunctionWithTrimstrs (added) org.hibernate.dialect.function.TypeQualifiedSQLFunction (added) You may think this code is relatively large as a dialect. It is because I also implemented user-defined function support. As HiRDB requires '?' parameters to be qualified by 'as <type>' in user-defined function invocations, I made a parser for the type declarations that the user specified in the properties file, and a renderer for the type qualifier. See javadoc comments of HiRDBDialect and UserFuncDeclParser for more details. This patch is created on Hibernate 3.2.5.ga and tested on HiRDB V8 with Type4 JDBC Driver. The example configuration for HiRDB is shown below: hibernate.dialect org.hibernate.dialect.HiRDBDialect hibernate.connection.driver_class JP.co.Hitachi.soft.HiRDB.JDBC.HiRDBDriver hibernate.connection.url jdbc:hitachi:hirdb://DBID=@HIRDBENVGRP=C:/hirdb.ini hibernate.connection.username hitachi hibernate.connection.password hitachi -- 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

11 years, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4079) Fail-fast a build using JDK6

by Andrew Lee Rubinger (JIRA)

Fail-fast a build using JDK6 ---------------------------- Key: HHH-4079 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4079 Project: Hibernate Core Issue Type: Improvement Environment: JDK6 Reporter: Andrew Lee Rubinger Attachments: HHH-4079.patch Emmanuel tells me that JDK5 is a requirement for building Hibernate Core. If JDK6 is an invalid choice, this patch will tell developers. -- 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

11 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3367) Add support to OpenEdge RDMS (Progress 10) in DialectFactory

by Glaucio Scheibel (JIRA)

Add support to OpenEdge RDMS (Progress 10) in DialectFactory ------------------------------------------------------------ Key: HHH-3367 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3367 Project: Hibernate3 Issue Type: Patch Components: core Affects Versions: 3.2.6 Reporter: Glaucio Scheibel Attachments: DialectFactory.java, DialectFactory.patch This patch adds OpenEdge (formely Progress Database) support to DialectFactory class. -- 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

11 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2654) Ingres dialect patch to support bit_length

by Chris Bredesen (JIRA)

Ingres dialect patch to support bit_length ------------------------------------------ Key: HHH-2654 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2654 Project: Hibernate3 Issue Type: Patch Components: core Reporter: Chris Bredesen Assignee: Steve Ebersole Priority: Minor Attachments: IngresDialect.diff This patch from Daniel fixes the Ingres dialect to support bit_length. -- 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

11 years, 3 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HV-296) Apply constraints on the elements of an Iterable instance

by Hardy Ferentschik (JIRA)

Apply constraints on the elements of an Iterable instance --------------------------------------------------------- Key: HV-296 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-296 Project: Hibernate Validator Issue Type: New Feature Components: engine Affects Versions: 4.0.2.GA Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik See BVAL-202 -- 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

11 years, 3 months

1
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4874) Embedded Objects get set to null if all its members are null

by Srinath (JIRA)

Embedded Objects get set to null if all its members are null ------------------------------------------------------------ Key: HHH-4874 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4874 Project: Hibernate Core Issue Type: Bug Components: annotations Reporter: Srinath Embedded Objects get set to null if all its members are null.i am facing this problem when i am having @Embeddable properties are null.even i creating instance in Parent class no-argument constructor.is there any other way to overcome from this issue? Thanks -- 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

11 years, 3 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3733) Introduce an annotation to disable ad-hoc null semantic of Hibernate components

by Vladimir Kovalyuk (JIRA)

Introduce an annotation to disable ad-hoc null semantic of Hibernate components ------------------------------------------------------------------------------- Key: HHH-3733 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3733 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Vladimir Kovalyuk see http://forums.hibernate.org/viewtopic.php?t=993972 For the model @Entity public class Person { private Address name = new Address(); ... @Embedded Address getAddress() {} } @Embeddable public class Address { public String getCity() {} public String getStreet() {} } the following xhtml excerpt causes NPE constantly when editing a person which address properties hasn't been filled in yet <h:inputText value="#{person.address.city}" /> I suggest introducing an annotation @Static which could be applied to Address class and lead to disabling null ad-hoc semantic on its instances. For some environments such as user interface this may be considered as the default behavior. I suggest introducing an Hibernate configuration parameter which would switch off the semantic. I would propose to consider embeddable classes as static mixins from OO design, not as just limited entities without identity. This point of view explains that embedded instance is a part of entity so it's lifecycle is the same as the entity's lifecycle. Thus constant presence of embeddable instance (property is never null) is the default behavior. Thus configuration parameter is "must have", not the thing which is "nice to have". >From the other hand null ad-hoc semantic is like dynamic mixins. So it would be nice to have a @Dynamic annotation to force this semantic for some components. -- 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

11 years, 3 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2308) Adjusting the Outer Join Predicate using Criteria Query

by Ben Grant (JIRA)

Adjusting the Outer Join Predicate using Criteria Query ------------------------------------------------------- Key: HHH-2308 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2308 Project: Hibernate3 Type: New Feature Components: query-criteria Versions: 3.2.1 Environment: Linux Using MS SQLServer Reporter: Ben Grant I have two tables Table A ||Col_1||Col_2|| |London| UK | |Liverpool| UK | | New York | USA | Table B ||Col_1||Col_2|| Col_3|| | UK | Europe | 0 | USA | Americas | 1 Using the Criteria class, Restriction Class and FetchMode, Hibernate manages to create a query that looks like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 where TableB3_.Col_3=1 When really i need the query to be like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 AND TableB3_.Col_3=1 currently their isn't any know way for hibernate to adjust or apply filters within the join clause. -- 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

11 years, 3 months

12
27
0 / 0

[Hibernate-JIRA] Created: (HHH-5436) different lock deepness for joined subclass

by kakusi kakusi (JIRA)

different lock deepness for joined subclass ------------------------------------------- Key: HHH-5436 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5436 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.2, 3.2.5 Environment: Oracle 10g Reporter: kakusi kakusi Hi, we use hibernate, oracle and pessimstic locking, to avoid concurrent modification through different threads. This worked fine for a while. But now we sometimes get deadlocks. We analyzied and found the cause: we produced locks with different deepnesses for objects of type joined subclass. An example for our kind of mapping: {noformat} <class name="TraceObject" table="TraceObjects"> <cache usage="read-write" /> <id name="objectId" column="objectId" type="long"> <generator class="native"> <param name="sequence">TraceObjectsSeq</param> </generator> </id> <timestamp name="dbVersionControl" /> ... </class> <joined-subclass name="VehicleObject" table="VehicleObjects" extends="TraceObject"> <key column="id" /> ... </joined-subclass>{noformat} Method: {{session.get(Class clazz, Serializable id, LockMode lockMode);}} Created Select-Statement: {{SELECT traceobjec0_.objectId ... FROM TraceObjects traceobjec0_ LEFT OUTER JOIN VehicleObjects traceobjec0_3_ ON traceobjec0_.objectId=traceobjec0_3_.id WHERE traceobjec0_.objectId=? FOR UPDATE;}} Effect: This locks the relevant data in table TraceObjects and joined table VehicleObjects. Method: {{session.get(Class clazz, Serializable id);}} {{session.lock(Object object, LockMode lockMode);}} Created Select-Statement: {{select traceobjec0_.objectId ... from TraceObjects traceobjec0_ left outer join VehicleObjects traceobjec0_3_ on traceobjec0_.objectId=traceobjec0_3_.id where traceobjec0_.objectId=?;}} {{select objectId from TraceObjects where objectId =? for update;}} Effect: This only locks the relevant data in table TraceObjects. We think this is a bug, because all techniques to lock should create the same lock type (only locking the parent table). -- 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

11 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5040) SQLQuery fails with auto-discovery of result set metadata and aliased columns

by Chris Wilson (JIRA)

SQLQuery fails with auto-discovery of result set metadata and aliased columns ----------------------------------------------------------------------------- Key: HHH-5040 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5040 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: 3.3.2 GA, MySQL Connector/J 5.0. Reporter: Chris Wilson Attachments: HibernateSqlQueryAliasTest.java Hibernate assumes that the column name returned by ResultSetMetaData#getColumnName(int) is the name it can use to extract the data from the ResultSet. However, if the SQLQuery uses column aliases, then this will fail here: {code|title=Stack Trace} org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:90) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2235) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2129) at org.hibernate.loader.Loader.list(Loader.java:2124) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:312) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1723) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:165) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:175) at org.wfp.rita.test.hibernate.HibernateSqlQueryAliasTest.testFailingWithAliases(HibernateSqlQueryAliasTest.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.wfp.rita.test.base.HibernateTestBase.runTestMethod(HibernateTestBase.java:204) at org.wfp.rita.test.base.HibernateTestBase.runTest(HibernateTestBase.java:117) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.sql.SQLException: Column 'id' not found. at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1075) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:989) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:984) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:929) at com.mysql.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1145) at com.mysql.jdbc.ResultSetImpl.getInt(ResultSetImpl.java:2814) at org.hibernate.type.IntegerType.get(IntegerType.java:51) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:210) at org.hibernate.loader.custom.CustomLoader$ScalarResultColumnProcessor.extract(CustomLoader.java:497) at org.hibernate.loader.custom.CustomLoader$ResultRowProcessor.buildResultRow(CustomLoader.java:443) at org.hibernate.loader.custom.CustomLoader.getResultColumnOrRow(CustomLoader.java:340) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:629) at org.hibernate.loader.Loader.doQuery(Loader.java:724) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2232) ... 26 more {code} Hibernate appears to support auto-discovery of result set columns, notwithstanding bug [HHH-436|http://opensource.atlassian.com/projects/hibernate/browse/HHH-436] which was closed as fixed. No QueryException is thrown if the returns of the query have not been defined. Instead, SQLQueryImpl.verifyParameters() sets SQLQueryImpl.autodiscovertypes, which ends up in QueryParameters.autodiscovertypes, which CustomLoader.doQuery() passes to CustomLoader.getResultSet(), which then calls CustomLoader.autoDiscoverTypes(), which calls ScalarResultColumnProcessor.performDiscovery(). performDiscovery() calls ResultSetMetaData#getColumnName() to retrieve each column name from the result set, which ends up in CustomLoader.ResultRowProcessor, where ScalarResultColumnProcessor.extract() tries to use it to extract data from the result set. Because the name doesn't match the actual alias used in the result set, this fails with the exception given above. [JDBC 4.0 Specification|http://jcp.org/aboutJava/communityprocess/final/jsr221/inde...] does not specify whether ResultSetMetaData.getColumnName() should return the name of the underlying column, or the name of the alias. It seems bizarre to me that it returns a value that cannot be passed to ResultSet.getObject(String). However, both MySQL and H2 take the position that we should call ResultSetMetaData.getColumnLabel() instead to get the name that can be used on the ResultSet: * [MySQL bug 21379|http://bugs.mysql.com/bug.php?id=21379] * [MySQL bug 21596|http://bugs.mysql.com/bug.php?id=21596] * [H2 mailing list discussion|http://www.mail-archive.com/h2-database@googlegroups.com/msg00...] The fix would appear to be modifying ScalarResultColumnProcessor.performDiscovery() (or CustomLoader.Metadata.getColumnName()) so that it calls getColumnLabel() instead of getColumnName(). The workaround is to explicitly specify column aliases with SQLQuery.addScalar(). Test case attached. -- 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

11 years, 3 months

5
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2010