October 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (BVAL-242) Extend the meta-data API to represent method-level constraints

by Gunnar Morling (JIRA)

Extend the meta-data API to represent method-level constraints -------------------------------------------------------------- Key: BVAL-242 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-242 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

14 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-243) Provide a means for specifying method parameter names

by Gunnar Morling (JIRA)

Provide a means for specifying method parameter names ----------------------------------------------------- Key: BVAL-243 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-243 Project: Bean Validation Issue Type: Sub-task Reporter: Gunnar Morling Emmanuel wrote: {quote} On named parameters we have three strategies I think: - not address the problem at all and use positional parameters to see what comes up JDK 8's hat (named parameters might not be represented as strings but rather as a typed object) - not address the problem in the specification but leave the API open enough for a provider to offer a named parameter friendly API - address the problem within the spec (the interface approach seems elegant) hoping for the named parameter to be represented as a String in JDK 8 I tend to like param0, param1 etc rather than arg0, arg1 but that's aesthetic. {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-244) Extend Validator API with methods for method validation

by Gunnar Morling (JIRA)

Extend Validator API with methods for method validation ------------------------------------------------------- Key: BVAL-244 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-244 Project: Bean Validation Issue Type: Sub-task Components: spec-general Reporter: Gunnar Morling Fix For: 1.1 {{javax.validation.Validator}} needs additional methods for method validation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-245) Define how method constraints are declared at parameters and return values

by Gunnar Morling (JIRA)

Define how method constraints are declared at parameters and return values -------------------------------------------------------------------------- Key: BVAL-245 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-245 Project: Bean Validation Issue Type: Sub-task Components: spec-general Reporter: Gunnar Morling Fix For: 1.1 Emmanuel: {quote} Constraints on parameters whose type is a subtype of the accepted types by the constraint are declared directly on the parameter void doHarm(@NotEmpty String kittenName); Constrains on parameters whose type is a constrained bean needs an annotation accepting the targeted groups. It was proposed to use @Valid for such case but [recent discussions|https://hibernate.onjira.com/browse/BVAL-208?focusedCommentId...] brought that back on the drawing board. There are a few notions floating around @Valid 1. cascade validation to nested beans 2. translate the validation of group A from the owning bean to validation of the group B on the nested bean (see BVAL-208) 3. define the group to validate in a method level validation About 3., I wonder if this should be part of Bean Validation or be part of the interception framework. In other words: * should it be an annotation provided / proposed by Bean Validation and recognized by interception techs like CDI, @Inject, Spring, AspectJ etc * should each interception tech provide its own annotation to specify the targeted group(s) {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5419) COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql

by Fabio Braga de Oliveira (JIRA)

COUNT operator with composite primary key and JPA 2.0 Criteria API produces bad sql ----------------------------------------------------------------------------------- Key: HHH-5419 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5419 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.0.Beta1, 3.5.4, 3.5.3, 3.5.2, 3.5.1 Environment: hibernate-entitymanager 3.6.0.Beta1, glassfish 3.0.1, linux ubuntu 10.04, MS SQL Server 2008 Reporter: Fabio Braga de Oliveira Attachments: hibernate-count-bug.zip Hibernate produces a invalid SQL if anyone use the count() operator with the JPA 2.0 Criteria API. Code: CriteriaBuilder cb = getEntityManager().getCriteriaBuilder(); CriteriaQuery<Object[]> cq = cb.createQuery(Object[].class); Root<EntityCompositePK> r = cq.from(EntityCompositePK.class); cq.multiselect(cb.count(r)); assertEquals(0, ((Long) (getEntityManager().createQuery(cq).getSingleResult())[0]).intValue()); I'm sending a little maven project which reproduces the bug. -- 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, 1 month

8
17
0 / 0

[Hibernate-JIRA] Created: (HHH-2548) when "order by" a composit object, which may be null, the result list returns only when the composit objcts not null

by Yu Deng (JIRA)

when "order by" a composit object, which may be null, the result list returns only when the composit objcts not null -------------------------------------------------------------------------------------------------------------------- Key: HHH-2548 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2548 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.3 Environment: tomcat 5.5, eclipse3.2, jre1.5, postgreSQL8.1, hibernate3 and hibernate3.2 Reporter: Yu Deng Priority: Critical <hibernate-mapping package="com.grapevinecs.ams.domain.perbranch.inv"> <class name="InvItem"> <id name="id" column="id"> <generator class="hilo"/> </id> ... <many-to-one name="transferredDetails"/>  .... </class> (another mapping file) </hibernate-mapping>> <hibernate-mapping package="com.grapevinecs.ams.domain.perbranch.inv"> <class name="InvTransferDetails" > <id name="id" column="id"> <generator class="hilo"/> </id> <property name="returnedToICBC" type="com.grapevinecs.ams.dao.BooleanInteger" not-null="true"/> ... </class> </hibernate-mapping> Probelm: 1) The result returns 3000 records ---- select count(*) from InvItem c where upper(c.invType) LIKE '%D%' and c.invSeries.closed = '0' and c.branch =60551 order by c.transferredDetails.returnedToICBC asc, c.stamp asc,c.invNmbr asc 2) result List return size 0 by this query --- from InvItem c where upper(c.invType) LIKE '%D%' and c.invSeries.closed = '0' and c.branch =60551 order by c.transferredDetails.returnedToICBC asc, c.stamp asc,c.invNmbr asc 1) is correct but 2) is not correct. only when transferredDetails in InvItem not null be returned. in case 2), I have no transferredDetails not null. after I excuted the query 2), even I remove "c.transferredDetails.returnedToICBC asc", the result is still return nothing. -- 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, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6570) Resolve component type

by Gail Badner (JIRA)

Resolve component type ---------------------- Key: HHH-6570 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6570 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Gail Badner Assignee: Gail Badner Fix For: 4.0.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6531) Initialize AbstractCollectionElement.elementValue and collection table primary key

by Gail Badner (JIRA)

Initialize AbstractCollectionElement.elementValue and collection table primary key ---------------------------------------------------------------------------------- Key: HHH-6531 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6531 Project: Hibernate Core Issue Type: Task Components: metamodel Reporter: Gail Badner Fix For: 4.0.0.next The following needs to be done before collections can be integrated into persisters: - AbstractCollectionElement.elementValue needs to be initialized - the primary key needs to be added to the collection table -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[Hibernate-JIRA] Created: (OGM-73) Log all operations to the datastore as a tool similar to show_sql or the logger equivalent

by Emmanuel Bernard (JIRA)

Log all operations to the datastore as a tool similar to show_sql or the logger equivalent ------------------------------------------------------------------------------------------ Key: OGM-73 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-73 Project: Hibernate OGM Issue Type: Improvement Components: core Reporter: Emmanuel Bernard -- 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, 1 month

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6344) IN expression misses negation when using row-value queries

by Isak Jonsson (JIRA)

IN expression misses negation when using row-value queries ---------------------------------------------------------- Key: HHH-6344 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6344 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.5 Environment: Using the PostgreSQL Dialect Tested on 3.6.5 and 3.6.0 with the same result. Works on 3.2, but there actual row value native queries are used Reporter: Isak Jonsson Attachments: MyEntity.java, MyRowValue.java The queries in the attached JPA entities behave differently regarding whether or not it is a row-value query. Test code using the attached entities: {noformat} List<Integer> values1 = new LinkedList<Integer>(); List<MyRowValue> values2 = new LinkedList<MyRowValue>(); values1.add(1); values1.add(2); values2.add(new MyRowValue(3,4)); values2.add(new MyRowValue(5,6)); em.createNamedQuery("MyEntity.query1").setParameter("values", values1).getResultList(); em.createNamedQuery("MyEntity.query2").setParameter("values", values1).getResultList(); em.createNamedQuery("MyEntity.query3").setParameter("values", values2).getResultList(); em.createNamedQuery("MyEntity.query4").setParameter("values", values2).getResultList(); {noformat} Results in the following SQL: {noformat} select myentity0_.id as id85_, myentity0_.a as a85_, myentity0_.b as b85_ from MyEntity myentity0_ where myentity0_.a in (? , ?) select myentity0_.id as id85_, myentity0_.a as a85_, myentity0_.b as b85_ from MyEntity myentity0_ where myentity0_.a not in (? , ?) select myentity0_.id as id85_, myentity0_.a as a85_, myentity0_.b as b85_ from MyEntity myentity0_ where myentity0_.a=? and myentity0_.b=? or myentity0_.a=? and myentity0_.b=? select myentity0_.id as id85_, myentity0_.a as a85_, myentity0_.b as b85_ from MyEntity myentity0_ where myentity0_.a=? and myentity0_.b=? or myentity0_.a=? and myentity0_.b=? {noformat} (No "NOT" in the last line) persistence.xml properties: {noformat} <property name="hibernate.hbm2ddl.auto" value="update"/> <property name="hibernate.show_sql" value="false"/> <property name="dialect" value="org.hibernate.dialect.PostgreSQLDialect" /> <property name="hibernate.use_sql_comments" value="true"/> {noformat} Thanks for any insight to 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

14 years, 1 month

2
3
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 October 2011