February 2013 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (BVAL-417) Mention "validationAppliesTo" in docs of @SupportedValidationTarget

by Gunnar Morling (JIRA)

12 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] (HHH-1523) Rebuild fetches from query-cache hits

by Julien Kronegg (JIRA)

12 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] (HHH-1523) Rebuild fetches from query-cache hits

by Julien Kronegg (JIRA)

12 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] (BVAL-322) Formatting and style improvements

by Gunnar Morling (JIRA)

12 years, 10 months

2
24
0 / 0

[Hibernate-JIRA] (HHH-7828) Warn when alias-specific lock modes are used in conjunction with follow-up locking

by Steve Ebersole (JIRA)

12 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-784) MapBinder.createFormulatedValue() does not honor DB schema name when creating query

by Sven Panko (JIRA)

MapBinder.createFormulatedValue() does not honor DB schema name when creating query ----------------------------------------------------------------------------------- Key: ANN-784 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-784 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.4.0.GA Environment: Hibernate 3.3.0.SP1, PostgresQL 8.3 Reporter: Sven Panko I detected a problem with a ManyToMany mapping using a Map in the following setup: @Entity @Table(name = "entitya", schema = "myschema") class EntityA { ... @ManyToMany(cascade = { CascadeType.PERSIST, CascadeType.MERGE }) @MapKey(name = "identifier") @JoinTable(name = "entitya_entityb", schema="myschema", joinColumns = @JoinColumn(name = "entitya_pk"), inverseJoinColumns = @JoinColumn(name = "entityb_pk")) @Cascade( { org.hibernate.annotations.CascadeType.SAVE_UPDATE, org.hibernate.annotations.CascadeType.DELETE_ORPHAN }) @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) private Map<String, EntityB> entityBMap = new HashMap<String, EntityB>(); } @Entity @Table(name = "entityb", schema = "myschema") class EntityB { ... } The SQL generated to load the entityBMap collection contains a subquery in the select clause, which looks like this: select a8.identifier from entityb a8 where a8.pk=entityb0_.entityb_pk (entityb0_.entityb_pk comes from the outer select clause) The problem here is, that entityb in the from clause is not prepended by the schema name "myschema" (the outer query is correctly doing this in the join clause, however). I tracked this down to the createFormulatedValue() method in the MapBinder class; the responsible code snippet is contained in lines 292 - 296: StringBuilder fromAndWhereSb = new StringBuilder( " from " ) .append( associatedClass.getTable().getName() ) //.append(" as ") //Oracle doesn't support it in subqueries .append( " " ) .append( alias ).append( " where " ); associatedClass.getTable().getName() does not return the fully qualified table name, so I think this should look something like this: StringBuilder fromAndWhereSb = new StringBuilder( " from " ); if (associatedClass.getTable().getSchema() != null) { fromAndWhereSb.append(associatedClass.getTable().getSchema()).append('.'); } fromAndWhereSb.append( associatedClass.getTable().getName() ) //.append(" as ") //Oracle doesn't support it in subqueries .append( " " ) .append( alias ).append( " where " ); -- 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

4
3
0 / 0

[Hibernate-JIRA] (BVAL-397) Align the JavaDoc on temps (return vs returns, define vs defines)

by Emmanuel Bernard (JIRA)

12 years, 10 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6736) Support for SELECT ... FOR UPDATE SKIP LOCKED / read past locking

by Aleksander Blomskøld (JIRA)

Support for SELECT ... FOR UPDATE SKIP LOCKED / read past locking ----------------------------------------------------------------- Key: HHH-6736 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6736 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Aleksander Blomskøld Hibernate does currently not support SKIP-LOCKED locking. Skip locked-semantics is useful in when having queue tables with several concurrent consumers. It is supported by Oracle (after 10g, documented in 11g), SQL Server (with the readpast hint), Sybase and possibly others. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
9
0 / 0

[Hibernate-JIRA] (BVAL-362) Reference the various specs (JPA, JSF, CDI, JavaBeans)

by Emmanuel Bernard (JIRA)

12 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] (BVAL-406) Should we add ConstraintDescriptor.getValidationAppliesTo()

by Emmanuel Bernard (JIRA)

12 years, 10 months

2
6
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 February 2013