August 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-478) Investigate whether a switch for turning off the instantiation of the method validation meta model makes sense

by Gunnar Morling (JIRA)

Investigate whether a switch for turning off the instantiation of the method validation meta model makes sense -------------------------------------------------------------------------------------------------------------- Key: HV-478 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-478 Project: Hibernate Validator Issue Type: Improvement Components: engine Reporter: Gunnar Morling Fix For: 4.x In HV 4.2 method validation was introduced. This requires the engine to gather and store meta data related to parameter and return value constraints. It might be useful to be able to disable the instantation of the method related meta model parts if method validation isn't used at all. Depending on the model size this could save computation time and memory. Probably it's useful to collect some statistics at first in order to find out whether implementing such a switch is worth the effort or not. -- 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, 11 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4700) ClassCastException with parameter in CaseNode.getFirstThenNode()

by Jean-Baptiste Mille (JIRA)

ClassCastException with parameter in CaseNode.getFirstThenNode() ---------------------------------------------------------------- Key: HHH-4700 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4700 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2, 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6, 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2.0.ga, 3.2.0.cr5, 3.2.0.cr4, 3.2.0.cr3, 3.2.0.cr2, 3.2.0 cr1 Environment: Hibernate 3.3.2.ga Reporter: Jean-Baptiste Mille Priority: Minor Attachments: testcase.zip Hql query with CASE .. WHEN and parameter in THEN clause throws a classCastException. Example : {code} UPDATE MyObject SET myProperty = CASE WHEN myFilterProperty like 'L%' THEN :new_value END {code} Exception java.lang.ClassCastException: org.hibernate.hql.ast.tree.ParameterNode cannot be cast to org.hibernate.hql.ast.tree.SelectExpression at org.hibernate.hql.ast.tree.CaseNode.getFirstThenNode(CaseNode.java:44) at org.hibernate.hql.ast.tree.CaseNode.getDataType(CaseNode.java:40) at org.hibernate.hql.ast.tree.BinaryLogicOperatorNode.extractDataType(BinaryLogicOperatorNode.java:210) at org.hibernate.hql.ast.tree.BinaryLogicOperatorNode.initialize(BinaryLogicOperatorNode.java:58) at org.hibernate.hql.ast.HqlSqlWalker.prepareLogicOperator(HqlSqlWalker.java:1133) at org.hibernate.hql.ast.HqlSqlWalker.evaluateAssignment(HqlSqlWalker.java:1043) at org.hibernate.hql.antlr.HqlSqlBaseWalker.assignment(HqlSqlBaseWalker.java:1086) at org.hibernate.hql.antlr.HqlSqlBaseWalker.setClause(HqlSqlBaseWalker.java:766) at org.hibernate.hql.antlr.HqlSqlBaseWalker.updateStatement(HqlSqlBaseWalker.java:361) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:239) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:254) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:185) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) at com.bnpparibas.eqd.DMLCaseTest.runQuery(DMLCaseTest.java:67) at com.bnpparibas.eqd.DMLCaseTest.doesntWork(DMLCaseTest.java:35) 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.junit.internal.runners.TestMethod.invoke(TestMethod.java:59) at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98) at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79) at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87) at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77) at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42) at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88) at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51) at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44) at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27) at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37) at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) 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) This issue have been [posted in user forum|https://forum.hibernate.org/viewtopic.php?f=1&t=981196&p=2369061&hi...]. It works with Hibernate 3.1.3. A test case (designed for Hibernate 3.3.2.ga) which illustrate this issue is 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, 11 months

5
6
0 / 0

[Hibernate-JIRA] Created: (BVAL-246) Create TCK tests for method validation

by Gunnar Morling (JIRA)

Create TCK tests for method validation -------------------------------------- Key: BVAL-246 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-246 Project: Bean Validation Issue Type: Sub-task Components: spec-general Reporter: Gunnar Morling Fix For: 1.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4947) Silent exclusion of null-valued map entry

by Tsering Shrestha (JIRA)

Silent exclusion of null-valued map entry ----------------------------------------- Key: HHH-4947 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4947 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-CR-1, 3.3.2 Reporter: Tsering Shrestha <class name="Product"> <id name="id"> <generator class="native"/> </id> <map name="sellingPrice"> <key column="PRODUCT" not-null="true" foreign-key="FK_SP_PRODUCT"/> <map-key type="string" column="model" not-null="true"/> <element type="double" column="price" not-null="false"/> </map> </class> Product product = new Product(); Product.getSellingPrice().put("XL",null); Product.getSellingPrice().put("L", 34.90); session.save(product) Gives the following SQL: insert into PRODUCT (id) values (null) call identity() insert into SELLINGPRICE (PRODUCT, MODEL, PRICE) values (?, ?, ?) And the SELLINGPRICE table indeed only has one row. Why does Hibernately *silently* remove my null-valued entry? I would either want it to be able to save the entry or raise an exception that it cannot. Report this post -- 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, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6679) SQL Server: Query with limit fails for HQL with 'DISTINCT'

by Piotr Findeisen (JIRA)

SQL Server: Query with limit fails for HQL with 'DISTINCT' ---------------------------------------------------------- Key: HHH-6679 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6679 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.7 Environment: Hibernate 3.6.7, Microsoft SQL Server 2008 Reporter: Piotr Findeisen When I issue HQL query like below (this query is of course simplified) with limit and/or offset (e.g. {{1}} and {{0}}) {code} SELECT u.id, (SELECT COUNT(DISTINCT role.id) FROM Role role) FROM User u {code} then Hibernate issues something like this to the SQL Server: {code} WITH query AS (select ROW_NUMBER() OVER (ORDER BY CURRENT_TIMESTAMP) as __hibernate_row_nr__, user0_.urid as col_0_0_, (select count(role1_.srid) from roles role1_) as col_1_0_ from users user0_ group by user0_.urid, (select count(role1_.srid) ) SELECT * FROM query WHERE __hibernate_row_nr__ BETWEEN ? AND ? {code} The above SQL is seriously malformed, it even has more opening brackets {{'('}} than closing {{')'}}. SQL Server response with obvious exception: {code} com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'SELECT'. {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-266) Create package-level JavaDoc for BV API

by Gunnar Morling (JIRA)

Create package-level JavaDoc for BV API --------------------------------------- Key: BVAL-266 URL: https://hibernate.onjira.com/browse/BVAL-266 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 final Reporter: Gunnar Morling Fix For: 1.1 Currently no package-level JavaDoc exists for the BV API (with the exception of {{javax.validation.groups}}). We should document all packages for BV 1.1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-553) Extract dedicated constraint module

by Gunnar Morling (JIRA)

Extract dedicated constraint module ----------------------------------- Key: HV-553 URL: https://hibernate.onjira.com/browse/HV-553 Project: Hibernate Validator Issue Type: Improvement Components: validators Reporter: Gunnar Morling Fix For: 5.x We should investigate the pro's and con's of extracting a new separate module {{hibernate-validator-constraints}} which holds all the custom constraints currently part of Hibernate Validator. Such a separate constraint module could be released independently from HV core and also be used with other BV providers if required. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6876) Hibernate doesn't support empty collection as parameter of javax.persistence.criteria.Expression "in" method parameter

by Yann Le Moigne (JIRA)

Hibernate doesn't support empty collection as parameter of javax.persistence.criteria.Expression "in" method parameter ---------------------------------------------------------------------------------------------------------------------- Key: HHH-6876 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6876 Project: Hibernate Core Issue Type: Bug Components: query-criteria, query-hql Affects Versions: 4.0.0.CR6 Environment: Using Mysql5.1 (org.hibernate.dialect.MySQL5InnoDBDialect) Reporter: Yann Le Moigne Looking at http://docs.oracle.com/javaee/6/api/javax/persistence/criteria/Expression..., there is nothing said about empty collection, so, we presume it is possible to use it. If this presumption is right, well hibernate break the spec because using empty collection as a parameter will end with something like "org.hibernate.hql.internal.ast.QuerySyntaxException: unexpected end of subtree [select generatedAlias0 from MyEntity as generatedAlias0 where generatedAlias0.id in ()] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2031) Add functions to Dialect that can disable use of schema and catalog parts -- for HSQLDB support

by Brian Holmes (JIRA)

Add functions to Dialect that can disable use of schema and catalog parts -- for HSQLDB support ----------------------------------------------------------------------------------------------- Key: HHH-2031 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2031 Project: Hibernate3 Type: Patch Components: core Versions: 3.1.3 Environment: This patch is against r9668 of /tags/v313/Hibernate3. Reporter: Brian Holmes Attachments: hibernate3-v313-support_schema_catalog_names.patch HSQLDB does not support the use of three part names, that is Tables with schema and catalog parts. This patch adds two functions to Dialect: supportsSchemaNames() and supportsCatalogNames(). Table.getQualifiedName() checks these values to decide whether to use or ignore the schema and catalog parts. By default these are enabled in Dialect. This patch only disables their use in HSQLDialect. This change is necessary for people who normally use Schema and Catalog names for access their primary database, but also use HSQLDB for Unit Testing. Without it, HSQLDB is unusable for Unit Testing because it fails on use of any catalog or schema names. -- 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, 12 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-249) Add unwrap method to ConstraintValidatorContext for provider extension

by Emmanuel Bernard (JIRA)

Add unwrap method to ConstraintValidatorContext for provider extension ---------------------------------------------------------------------- Key: BVAL-249 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-249 Project: Bean Validation Issue Type: New Feature Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 12 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2012