hibernate-issues February 2013

hibernate-issues@lists.jboss.org

1 participants
444 discussions

[Hibernate-JIRA] (BVAL-358) Make ExecutableDescriptor#validateConstructorParameters() and validateConstructorReturnValue() more usable

by Gunnar Morling (JIRA)

12 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5976) ClassCastException when accessing attributes of embedded object through Join structure.

by Jaroslaw Lewandowski (JIRA)

ClassCastException when accessing attributes of embedded object through Join structure. --------------------------------------------------------------------------------------- Key: HHH-5976 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5976 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.6.0 Reporter: Jaroslaw Lewandowski Suppose you have class A which has attribute 'a' of type E which is @Embedded type. The following code using criteria API will throw ClassCastExeption {code} Root<A> root =... Join<A,E> join = root.join(A_.e); join.get(E_.attribute); <=== accessing any attribute of E will throw ClassCastExeption. With the following stack trace:\ {code} {code} java.lang.ClassCastException: org.hibernate.ejb.metamodel.SingularAttributeImpl cannot be cast to javax.persistence.metamodel.ManagedType at org.hibernate.ejb.criteria.path.AbstractFromImpl.locateManagedType(AbstractFromImpl.java:151) at org.hibernate.ejb.criteria.path.AbstractFromImpl.locateAttributeInternal(AbstractFromImpl.java:145) at org.hibernate.ejb.criteria.path.AbstractPathImpl.locateAttribute(AbstractPathImpl.java:216) at org.hibernate.ejb.criteria.path.AbstractPathImpl.get(AbstractPathImpl.java:189) {code} -- 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, 1 month

2
3
0 / 0

[Hibernate-JIRA] (BVAL-364) Clarify whether or not the metadata API ignore the method enable/disable settings

by Emmanuel Bernard (JIRA)

12 years, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3644) Add support for "WITH UR" isolation clause on DB2

by Ricardo Fernandes (JIRA)

Add support for "WITH UR" isolation clause on DB2 ------------------------------------------------- Key: HHH-3644 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3644 Project: Hibernate Core Issue Type: Sub-task Components: core Affects Versions: 3.3.1 Environment: HIbernate 3.3.1 / DB2 9.x Reporter: Ricardo Fernandes The question is basically the same as Steve's, i.e. to force DB2 to use as few locks as possible on heavy load scenarios. Although some might consider the use of the WITH UR clause a bad approach (since it allows dirty reads), the fact is that there are some cases where this is in fact acceptable, such as computing the total amount of rows of a query (for information purposes) or producing a high-level listing of items with very little detailed info. The bottom line is: if I need to trade performance for extremely accurate data, I surely want to be able to decide when this should happen. I've already performed the changes that makes it possible to use both the FOR READ ONLY and the WITH UR clauses and I will be submitting a patch shortly so you can have a look at it. The strategy I've used was basically the following: 1. Added two new methods on the Dialect class: String getDatabaseReadOnlyString(String sql) - for adding the READ ONLY clause String getDirtyReadsString(String sql) - for adding the WITH UR clause 2. Changed the Query interface in order to allow the user to say whether he/she wants the query to allow dirty reads: Query setAllowDirtyReads(boolean allowDirtyReads); 3. Added a default implementation on the AbstractQueryImpl which initializes the flag a false 4. Added a similar attribute on the QueryParameters class 5. Changed the prepareQueryStatement() method of the Loader class (just after the useLimit part in order: a) Ask the dialect for the getDatabaseReadOnlyString() is there are no LockModes set (as did Steve) b) Ask the dialect for the getDirtyReadsString() is the queyParameters allows dirty reads. All the tests were well succeeded. Hope you find these changes, at least, worth looking at. Best Regards, Ricardo -- 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, 1 month

7
10
0 / 0

← Newer
1
...
42
43
44
45
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2013