February 2012 - hibernate-issues - Jboss List Archives

[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

12 years, 10 months

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

12 years, 10 months

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

12 years, 10 months

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

12 years, 10 months

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

12 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-7123) Many-to-one domain model is configured as org.hibernate.metamodel.spi.domain.BasicType

by Gail Badner (JIRA)

Many-to-one domain model is configured as org.hibernate.metamodel.spi.domain.BasicType --------------------------------------------------------------------------------------- Key: HHH-7123 URL: https://hibernate.onjira.com/browse/HHH-7123 Project: Hibernate ORM Issue Type: Bug Reporter: Gail Badner Assignee: Gail Badner Many-to-one domain model should be configured as org.hibernate.metamodel.spi.domain.Entity. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-7119) Hibernate filter's parameters are not populated when an entity's Collection is populated using a fetch mode of subselect.

by Aaron Trewern (JIRA)

Hibernate filter's parameters are not populated when an entity's Collection is populated using a fetch mode of subselect. ------------------------------------------------------------------------------------------------------------------------- Key: HHH-7119 URL: https://hibernate.onjira.com/browse/HHH-7119 Project: Hibernate ORM Issue Type: Bug Affects Versions: 3.5.2 Reporter: Aaron Trewern I have a @Filter on a collection property that has @Fetch(FetchMode.SUBSELECT) when I query this entity with a simple list() I can see the filter is also being applied to SQL generated to retrieve the collection property but the "?" positional parameter is not being set in the subquery. For the purposes of illustration I have simplified the Filter from the actual IN clause to an equality test. A similar problem was reported here https://forum.hibernate.org/viewtopic.php?f=1&t=1007658&start=0&sid=a797c... The entity in question has a number of collection properties all of which were fetched with a Fetchmode.SUBSELECT, after adding the @Filter I was only able to make the query work with a FetchMode.JOIN or SELECT. But the query seemed much slower. In the code box blow you can see Hibernate correctly binding the userId parameter to the query for retrieving the main entity: {code} 27.02.2012 17:02:17 DEBUG [http-8080-1] (SQLStatementLogger:logStatement) - select job0_.id as id1_, job0_.ENTITY_UID as ENTITY2_1_, job0_.version as version1_, job0_.created_by_user_id as created4_1_, job0_.created_on as created5_1_, job0_.internal_notes as internal6_1_, job0_.job_status_id as job7_1_, job0_.job_status_updated as job8_1_, job0_.job_status_user_id as job9_1_, job0_.job_type_id as job10_1_, job0_.name as name1_, job0_.number as number1_, job0_1_.assigned_to_employee_id as assigned1_2_, job0_1_.is_active as is2_2_, job0_1_.owner_party_id as owner3_2_, job0_2_.city as city6_, job0_2_.country as country6_, job0_2_.county as county6_, job0_2_.line1 as line4_6_, job0_2_.line2 as line5_6_, job0_2_.state as state6_, job0_2_.zipcode as zipcode6_, job0_2_.building_size as building8_6_, job0_2_.building_size_unit_id as building9_6_, job0_2_.building_type_id as building10_6_, job0_3_.annual_salary as annual1_17_, job0_3_.employed_by_department_id as employed2_17_, job0_3_.employee_number as employee3_17_, job0_3_.hourly_rate as hourly4_17_, job0_3_.last_hire_date as last5_17_, job0_3_.person_id as person6_17_, job0_4_.asset_id as asset1_48_, job0_4_.bid_submission_deadline as bid2_48_, job0_4_.customer_party_id as customer3_48_, job0_4_.original_contract_amount as original4_48_, job0_4_.payment_application_day as payment5_48_, job0_4_.requested_completion_date as requested6_48_, job0_4_.requested_start_date as requested7_48_, job0_5_.credit_limit as credit1_52_, job0_5_.party_id as party2_52_, case when job0_2_.id is not null then 2 when job0_1_.id is not null then 1 when job0_3_.id is not null then 3 when job0_4_.id is not null then 4 when job0_5_.id is not null then 5 when job0_.id is not null then 0 end as clazz_ from edrjob job0_ left outer join edrassetjob job0_1_ on job0_.id=job0_1_.id left outer join edrbuildingjob job0_2_ on job0_.id=job0_2_.id left outer join edremployeejob job0_3_ on job0_.id=job0_3_.id left outer join edrprojectjob job0_4_ on job0_.id=job0_4_.id left outer join edrrelationshipjob job0_5_ on job0_.id=job0_5_.id where ? = 113 and (job0_.id in (select department1_.job_id from edrdepartmentjoblink department1_ where department1_.department_id=2)) limit ? 27.02.2012 17:02:17 TRACE [http-8080-1] (NullableType:nullSafeSet) - binding '113' to parameter: 1 {code} In code box below you can see Hibernate failing to set the parameter for the subselect query used to retrieve the collection property details: {code} 27.02.2012 17:02:32 DEBUG [http-8080-1] (SQLStatementLogger:logStatement) - select parties0_.job_id as job7_1_1_, parties0_.id as id1_, parties0_.id as id32_0_, parties0_.ENTITY_UID as ENTITY2_32_0_, parties0_.version as version32_0_, parties0_.description as descript4_32_0_, parties0_.job_id as job7_32_0_, parties0_.party_id as party5_32_0_, parties0_.party_type_id as party6_32_0_ from edrjobpartylink parties0_ where parties0_.job_id in (select job0_.id from edrjob job0_ left outer join edrassetjob job0_1_ on job0_.id=job0_1_.id left outer join edrbuildingjob job0_2_ on job0_.id=job0_2_.id left outer join edremployeejob job0_3_ on job0_.id=job0_3_.id left outer join edrprojectjob job0_4_ on job0_.id=job0_4_.id left outer join edrrelationshipjob job0_5_ on job0_.id=job0_5_.id where ? = 113 and (job0_.id in (select department1_.job_id from edrdepartmentjoblink department1_ where department1_.department_id=2))) 27.02.2012 17:02:32 WARN [http-8080-1] (JDBCExceptionReporter:logExceptions) - SQL Error: 0, SQLState: 07001 27.02.2012 17:02:32 ERROR [http-8080-1] (JDBCExceptionReporter:logExceptions) - No value specified for parameter 1 {code} {code:title=Job.java|borderStyle=solid} @FilterDefs({ @FilterDef( name = "filterJobsByUserId", parameters = { @ParamDef (name = "userId", type = "java.lang.Integer") } ) }) @Entity @Filters({ @Filter(name="filterJobsByUserId", condition = ":userId = 113") }) public class Job extends LockableBaseEntity implements Auditable { ... @OneToMany(mappedBy="job", targetEntity=JobParty.class, fetch=FetchType.EAGER, cascade=CascadeType.ALL, orphanRemoval=true) @Fetch(FetchMode.SUBSELECT) private Set<JobParty> parties = new HashSet<JobParty>(); public Set<JobParty> getParties() { return this.parties; } public void setParties (Set<JobParty> parties) { this.parties = parties; } ... } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
9
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

12 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1028) Use index update operations when possible

by Sanne Grinovero (JIRA)

Use index update operations when possible ----------------------------------------- Key: HSEARCH-1028 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-1028 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Critical Fix For: 4.1.0.Alpha1 IndexWriter is exposing a method org.apache.lucene.index.IndexWriter.updateDocument(Term, Document, Analyzer) which allows faster updates, and guarantees atomicity from the query point of view. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
7
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

12 years, 10 months

2
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 February 2012