April 2012 - hibernate-issues - Jboss List Archives

[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

11 years, 4 months

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

11 years, 4 months

7
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3869) Improve toString on SessionStatistics

by David Sheldon (JIRA)

Improve toString on SessionStatistics ------------------------------------- Key: HHH-3869 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3869 Project: Hibernate Core Issue Type: Patch Components: core Reporter: David Sheldon Priority: Trivial Attachments: sessionstats.diff toString on SessionStatisticsImpl is missing a comma - patch attached. Before: SessionStatistics[entity count=100collection count=1100] After: SessionStatistics[entity count=100,collection count=1100] -- 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, 4 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3862) Wrong link in documentation tutorial chapter 1

by Christian Bauer (JIRA)

Wrong link in documentation tutorial chapter 1 ---------------------------------------------- Key: HHH-3862 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3862 Project: Hibernate Core Issue Type: Bug Components: documentation Reporter: Christian Bauer Priority: Trivial Hi my name is Rafael. Just to let you know that in this page http://www.hibernate.org/hib_docs/v3/reference/en/html/tutorial-firstapp.... in the *Note* item the link maven is break. This link is point to http://maven.org instead of point to http://maven.apache.org. Let it! Regards, -- 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, 4 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3458) Register postgres random() function as "rand" in PostgresSQLDialect

by Stephen Cresswell (JIRA)

Register postgres random() function as "rand" in PostgresSQLDialect ------------------------------------------------------------------- Key: HHH-3458 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3458 Project: Hibernate3 Issue Type: Improvement Components: build Affects Versions: 3.2.5 Environment: Postgres 8.3 Reporter: Stephen Cresswell Priority: Trivial I have an HQL query which uses "order by rand()". This works fine in our local integration tests (which are run against hsqldb), but fails against our build integration tests which runs postgres. The reason the query fails is because postgres function for "rand" is called "random". We can workaround this by dynamically detecting the db driver and generating db specific queries, but it strikes me that the cleanest solution for this is to simply re-register postgres' random function as "rand" in the PostgresSQLDialect, i.e. registerFunction( "random", new NoArgSQLFunction("random", Hibernate.DOUBLE) ); registerFunction( "rand", new NoArgSQLFunction("random", Hibernate.DOUBLE) ); -- 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, 4 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6643) Criteria doesn't support a chaining of 2 not restrictions (sql = not not criterion)

by Lorber Sebastien (JIRA)

Criteria doesn't support a chaining of 2 not restrictions (sql = not not criterion) ----------------------------------------------------------------------------------- Key: HHH-6643 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6643 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.2.7 Environment: Oracle 10g Hibernate 3.2.7 Reporter: Lorber Sebastien Priority: Trivial When we do: "Restrictions.not( Restrictions.not( Restrictions.eq("field",3) ) );" Hibernate generates "where not not field=3" Which generates an SQL exception The correct SQL syntax is: "where not (not field=3)" (At least our Oracle) I think Hibernate should handle such a case. /!\ See org.hibernate.criterion.NotExpression#toSqlString It seems that for MySQLDialect the parenthesis are added, but not for other dialects... I don't know the sql specificities of all dialects but perhaps the parenthesis should be added also for oracle dialect? Note that we use a custom dialect, extending Oracle10gDialect For those interested: i'm doing two not on a criterion instead of using the criterion directly. In real world, my code sample would be a little more complex: sometimes we compose with a lot of criterions, in many different methods. So i do not exactly use Restrictions.not( Restrictions.not( criterion ) ); Trust me, bad luck, it happened that the dynamic composition of my restrictions, in one specific case, resulted on a double not restriction applied to a criterion. Note that an easy workaround of this is to "add the parenthesis manually". A conjunction is a bit like an "empty restriction" thus what i've done is: Restrictions.not( Restrictions.and( Restrictions.not( Restrictions.eq("field",3) ), Restrictions.conjunction() ) ); Adding the "not criterion" into conjunction containing only the criterion. This way, the sql of my inner not restriction become something like: ( not field = 3 AND 1=1 ) -> We can apply a not on that, while we weren't able on "not field = 3" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2805) The class Order does not contain getters

by Aviad Lichtenstadt (JIRA)

The class Order does not contain getters ---------------------------------------- Key: HHH-2805 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2805 Project: Hibernate3 Issue Type: Improvement Components: query-criteria Affects Versions: 3.2.5 Reporter: Aviad Lichtenstadt Priority: Trivial Attachments: HibernateOrder.txt The class Order does not contain getters. This is way it is impossible to know if the ignoreCase field was set. This issue becomes more important using Hibernate Shards project. Using Shards the ordering is done using java and there is no way today to know is this property is set. i am applying a patch that adds this getter -- 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, 4 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2721) PostgreSQLDialect: function md5() always returns a string value

by Dirk Leser (JIRA)

PostgreSQLDialect: function md5() always returns a string value --------------------------------------------------------------- Key: HHH-2721 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2721 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4.sp1 Reporter: Dirk Leser Priority: Minor The md5() function always returns a string type and not the type given as parameter. Therefore the line registerFunction( "md5", new StandardSQLFunction("md5") ); has to be changed to registerFunction( "md5", new StandardSQLFunction("md5", Hibernate.STRING) ); in class org.hibernate.dialect.PostgreSQLDialect -- 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, 4 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3788) FirebirdDialect: current_date() function

by Rafael Santini (JIRA)

FirebirdDialect: current_date() function ---------------------------------------- Key: HHH-3788 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3788 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.1 Environment: 3.3.1, Firebird 1.5 Reporter: Rafael Santini The FirebirdDialect does not supports current_date() function. A select like "select * from test where dt < current_date()" causes the following exception: --- Caused by: org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544569. Dynamic SQL Error SQL error code = -104 Token unknown - line 1, column X ( --- In MySQLDialect.java there is: registerFunction("current_date", new NoArgSQLFunction("current_date", Hibernate.DATE, false) ); But in InterbaseDialect.java or FirebirdDialect.java there is not the current_date function. -- 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, 4 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2448) Generate identical column aliases among cluster

by Loïc LEFEVRE (JIRA)

Generate identical column aliases among cluster ----------------------------------------------- Key: HHH-2448 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2448 Project: Hibernate3 Type: Improvement Components: query-sql Versions: 3.2.2 Environment: Hibernate version: 3.2.2, 2.1.8 Database: Oracle 9.2.0.8 Reporter: Loïc LEFEVRE Attachments: report_1.txt, report_2.txt Among our weblogic cluster (12 instances), we can see that a query can have different column aliases. Although all seems correct, when regarding database reports like StatsPack or Spotlight we can see that because of these different aliases, the reports are wrong. Indeed, a resource consuming query can see its associated report properties (cpu usage, buffer gets, number of executions...) divided by the number of weblogic instances of our cluster (i.e. divided by 12) thus preventing us to pinpoint the queries to look at. On a 3 instances cluster, we can see this report: REPORT#1: one statement with a poor number of buffer gets/execution is reported splitted in 3, see the alias generated for column DTO.CREATION_DATE for example On a 4 instances cluster, we can see this report: REPORT#2: one statement responsible of the latch free/cache buffers chains wait events splitted in 4, note the column alias generated fordeffcashcy0_.BEST_EXPECTED_CY More than confusing the DBAs about the same query with n different "faces", our reports don't show us all the queries to look at: indeed, in our "Top 50 queries", a lot of them are duplicates! Also the memory required in the SGA to store the queries, the execution plan and so on is increased... Finally, although the column aliases can have up to 30 characters under Oracle, the limit is set to 10, why? -- 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, 4 months

15
43
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2012