March 2009 - hibernate-issues - Jboss List Archives

[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, 2 months

7
10
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, 2 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, 2 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, 2 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, 2 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, 2 months

15
43
0 / 0

[Hibernate-JIRA] Created: (HHH-3811) Bug: No ability to escape SQL keywords in HQL queries.

by John Roberts (JIRA)

Bug: No ability to escape SQL keywords in HQL queries. ------------------------------------------------------ Key: HHH-3811 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3811 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.CR1 Environment: 3.3.0.CR1, MS SQL Server 2005 Express Reporter: John Roberts Priority: Critical There appears to be no way to escape property names that are SQL keywords in HQL queries. For example, if you have a property named "key", which is a reasonable name for a property, and you are constructing an HQL query, e.g.: session.createQuery("select from Entities where key=?"); That will fail on MS SQL Server, because "key" is a reserved T-SQL keyword. However, there is no way to make it succeed, as either an absent-minded developer appears to have forgotten to add the ability to escape keywords to HQL (oops), or it's the secret of the millennium and was left out of the documentation on purpose (it has certainly boggled the minds of the folks on FreeNode #java, #hibernate, and the hibernate forum). Note that none of the following will succeed (this is what I have tried so far): session.createQuery("select from Entities where key=?"); session.createQuery("select from Entities where [key]=?"); // <-- mssql style still fails to be parsed session.createQuery("select from Entities where `key`=?"); session.createQuery("select from Entities where 'key'=?"); session.createQuery("select from Entities where \"key\"=?"); session.createQuery("select from Entities where ''key''=?"); session.createQuery("select from Entities where {key}=?"); session.createQuery("select from Entities where <key>=?"); session.createQuery("select from Entities where (key)=?"); session.createQuery("select from Entities where $key$=?"); session.createQuery("select from Entities where $key=?"); Note that using the underlying DBMS's escape method *does* work for column names in the entity mappings, but does not work in actual HQL. Since most DBMS's have their own dialects of SQL, the inability to escape keywords in HQL means that it is generally impossible to guarantee that any given HQL query will work unless you specifically design your application around the underlying DBMS (which is precisely one of the things you were hoping to avoid with Hibernate -- although on the other hand you're already tied to the DBMS with escaped keywords in the entity mapping anyways). -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3818) Hibernate/JBC integration doesn't property handle Entity/CollectionRegionAccessStrategy evict

by Brian Stansberry (JIRA)

Hibernate/JBC integration doesn't property handle Entity/CollectionRegionAccessStrategy evict --------------------------------------------------------------------------------------------- Key: HHH-3818 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3818 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.3.1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.3.x EntityRegionAccessStrategy and CollectionRegionAccessStrategy have evict(Object key) and evictAll() that say they must cause removal of items from the cache "immediately without regard for transaction isolation." The Hibernate/JBC integration is not properly handling this as the JBC removeNode calls it makes are not dealing with transactional issues. The integration needs to: 1) Perhaps suspend any ongoing tx (particularly since these calls are typically made from a tx Synchronization's afterCompletion() callback, when the tx is Status.COMMITTED and it isn't appropriate to call into the cache expecting the cache to incorporate the call into the transaction. (Alhthough I believe JBC handles this correctly by ignoring the tx, since it isn't ACTIVE). 2) Deal with the fact that the tx that is being committed is likely holding locks in JBC. This is the big issue. I believe dealing with this will a) require keeping state in the Hib/JBC integration layer's Region to track that an eviction has occurred but may not be reflected in JBC b) using JBC as a notification bus to propagate the fact of the eviction to other nodes c) attempting to evict the data from JBC locally, failing promptly in the face of lock conflicts d) including in any get() or putFromLoad() calls logic to check the state from a), again attempting to evict locally (with a very short timeout) if not yet evicted and not allowing calls to proceed into JBC until successful. -- 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, 2 months

8
17
0 / 0

[Hibernate-JIRA] Created: (ANN-787) @UniqueConstraint annotation not creating unique indexes

by Avinash THM (JIRA)

@UniqueConstraint annotation not creating unique indexes -------------------------------------------------------- Key: ANN-787 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-787 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: hibernate-core 3.3.1GA, hibernate-annotations 3.4.0GA, DB2 version 9.1 Reporter: Avinash THM Priority: Minor Unique indexes are not being created when using @UniqueConstraint annotation. The tables are created properly with primary keys and foreign keys, but the unique indexes are not created. I have posted the issue in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=991505&highlight=) but didnt get any reply. I have also seen a couple of posts for the same problem. can anybody help me out with this issue? -- 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, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3465) HiRDB Support

by Tomoto Shimizu Washio (JIRA)

HiRDB Support ------------- Key: HHH-3465 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3465 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.5 Environment: 3.2.5 + HiRDB V8 + Type4 JDBC Driver Reporter: Tomoto Shimizu Washio Attachments: hirdbdialect.patch I would like to contribute with a dialect for HiRDB, Hitachi's RDBMS. (For more information, please see http://www.hitachi.co.jp/Prod/comp/soft1/global/prod/hirdb/) I added 4 classes and slightly modified 2 existing classes as shown below. Please look at the documentation at the top of the patch for explanations. org.hibernate.dialect.HiRDBDialect (added) org.hibernate.dialect.UserFuncDeclParser (added) org.hibernate.dialect.DialectFactory (modified) org.hibernate.dialect.function.AnsiTrimEmulationFunction (modified) org.hibernate.dialect.function.AnsiTrimEmulationFunctionWithTrimstrs (added) org.hibernate.dialect.function.TypeQualifiedSQLFunction (added) You may think this code is relatively large as a dialect. It is because I also implemented user-defined function support. As HiRDB requires '?' parameters to be qualified by 'as <type>' in user-defined function invocations, I made a parser for the type declarations that the user specified in the properties file, and a renderer for the type qualifier. See javadoc comments of HiRDBDialect and UserFuncDeclParser for more details. This patch is created on Hibernate 3.2.5.ga and tested on HiRDB V8 with Type4 JDBC Driver. The example configuration for HiRDB is shown below: hibernate.dialect org.hibernate.dialect.HiRDBDialect hibernate.connection.driver_class JP.co.Hitachi.soft.HiRDB.JDBC.HiRDBDriver hibernate.connection.url jdbc:hitachi:hirdb://DBID=@HIRDBENVGRP=C:/hirdb.ini hibernate.connection.username hitachi hibernate.connection.password hitachi -- 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, 2 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2009