April 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2381) Criteria API : Order by Native SQL

by Sami Dalouche (JIRA)

Criteria API : Order by Native SQL ----------------------------------- Key: HHH-2381 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2381 Project: Hibernate3 Type: Improvement Components: query-criteria Reporter: Sami Dalouche Hi, It would be nice to be able to specify the ORDER BY clause using Native SQL. (It is currently doable by subclassing the Order class, but some nice solution would allow the order to specify attributes on another table..) Let's take a simple example : I have a distance("attribute", geometry) function, that is of course, proprietary. I am quering table A, which I can join to table B to get the "attribute", on which I want to apply my distance() function. If I create my own Order subclass, and addOrder on the criteria, the distance("attribute, geometry) is going to refer to the main criteria's class mapping. So, something like addOrder("objectpath.joined", new MyOrder(...)); would be perfect. What do you think ? Regards, Sami Dalouche -- 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, 1 month

4
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2045) in () result in "unexpected end of subtree"

by Max Rydahl Andersen (JIRA)

in () result in "unexpected end of subtree" -------------------------------------------- Key: HHH-2045 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2045 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Reporter: Max Rydahl Andersen "in ()" is a valid sql construct and works with previous versions of Hibernate. The new parser throws an "unexpected end of subtree". example: from Animal an where an.id in () or from Animal an where an.id in (:list) and input list is an empty list. Is this the behavior we want from now on or ? -- 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, 1 month

10
18
0 / 0

[Hibernate-JIRA] Created: (HHH-2054) Persistent wrapper collections should support generics

by Daniel Kandel (JIRA)

Persistent wrapper collections should support generics ------------------------------------------------------ Key: HHH-2054 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2054 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr2 Reporter: Daniel Kandel Hibernate persistent wrapper collections - classes that extend AbstractPersistentCollection and implement map, set or list (like PersistentSet and PersistentList), should support generics (PersistentSet<String>, PersistentMap<Integer, String>). In order to create a custom collection, one must extend one of these classes, but then the new collection cannot support generics. -- 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, 1 month

4
4
0 / 0

[Hibernate-JIRA] Created: (ANN-469) bulk update with native sql queries

by Amir Pashazadeh (JIRA)

bulk update with native sql queries ----------------------------------- Key: ANN-469 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-469 Project: Hibernate Annotations Type: Improvement Components: binder Versions: 3.2.0.ga Reporter: Amir Pashazadeh Priority: Critical Hibernate Annotations 3.2 does not support bulk update/deletes using native queries, if I have something like: @NamedNativeQuery(name = "testQuery", query = "delete from tb_test where id = ?") in one of my entities, there will be following exception during build of SessionFactory : Exception in thread "main" org.hibernate.cfg.NotYetImplementedException: Pure native scalar queries are not yet supported at org.hibernate.cfg.annotations.QueryBinder.bindNativeQuery(QueryBinder.java:118) at org.hibernate.cfg.annotations.QueryBinder.bindNativeQueries(QueryBinder.java:197) at org.hibernate.cfg.AnnotationBinder.bindQueries(AnnotationBinder.java:281) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:404) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:452) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:268) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1210) ------ I made a mistake and I reported this issue as HHH-2147 as an issue about Hibernate core! :( -- 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, 1 month

11
16
0 / 0

[Hibernate-JIRA] Created: (HHH-2403) Support multi-line import.sql files

by Christian Bauer (JIRA)

Support multi-line import.sql files ----------------------------------- Key: HHH-2403 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2403 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.2 Reporter: Christian Bauer I leave this as Major, because it most likely breaks all existing import.sql's. The statement delimiter in import.sql is currently a newline. We need to change that to: - delimiter is semicolon, so users can copy/paste stuff from and to SQL consoles - newline is a real newline, allows users to enter newlines into larger text columns without a 5000 character wide line -- 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, 1 month

11
27
0 / 0

[Hibernate-JIRA] Created: (HHH-2171) Transaction Rollback Problem in GA due to jboss cache alpha dependency

by bhumika thakkar (JIRA)

Transaction Rollback Problem in GA due to jboss cache alpha dependency ---------------------------------------------------------------------- Key: HHH-2171 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2171 Project: Hibernate3 Type: Bug Components: build Versions: 3.2.0.ga Reporter: bhumika thakkar We upgraded to Hibernate GA, and started getting Transaction Rolloback Exception. GA release is distributed with JBoss cache alpha quality dependency. Upgrading to the current production release of it fixes the issue. Stack trace: org.jboss.cache.interceptors.TxInterceptor.runRollbackPhase Rollback had a problem java.lang.IllegalStateException: local transaction Transaction[] transaction does not match running tx null at org.jboss.cache.interceptors.TxInterceptor.handleCommitRollback(TxInterc eptor.java:616) at org.jboss.cache.interceptors.TxInterceptor.runRollbackPhase(TxIntercepto r.java:696) at org.jboss.cache.interceptors.TxInterceptor$RemoteSynchronizationHandler. afterCompletion(TxInterceptor.java:947) at org.jboss.cache.interceptors.OrderedSynchronizationHandler.afterCompleti on(OrderedSynchronizationHandler.java:80) at com.caucho.transaction.TransactionImpl.callAfterCompletion(TransactionIm pl.java:893) at com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:713) at com.caucho.transaction.TransactionManagerImpl.commit(TransactionManagerI mpl.java:263) at com.caucho.jca.UserTransactionImpl.commit(UserTransactionImpl.java:411) at com.caucho.jca.UserTransactionProxy.commit(UserTransactionProxy.java:142 ) at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTr ansactionManager.java:787) at org.springframework.transaction.support.AbstractPlatformTransactionManag er.processCommit(AbstractPlatformTransactionManager.java:500) at org.springframework.transaction.support.AbstractPlatformTransactionManag er.commit(AbstractPlatformTransactionManager.java:473) at org.springframework.transaction.interceptor.TransactionAspectSupport.doC ommitTransactionAfterReturning(TransactionAspectSupport.java:267) at org.springframework.transaction.interceptor.TransactionInterceptor.invok e(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(Ref lectiveMethodInvocation.java:170) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAo pProxy.java:176) at $Proxy119.executeCallback(Unknown Source) ... -- 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, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2218) java.util.ConcurrentModificationException at org.hibernate.pretty.Printer.toString(Printer.java:90)

by rm (JIRA)

java.util.ConcurrentModificationException at org.hibernate.pretty.Printer.toString(Printer.java:90) --------------------------------------------------------------------------------------------------- Key: HHH-2218 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2218 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: Hibernate 3.1.3, spring 2.1.8 on Jboss 4.0.2 with Oracle 10g Reporter: rm Similar issues have been logged since May 2005 and have been marked as 'Fixed' by Gavin especially for Session.toString() related cases. However, I am also facing similar issues in Printer.toString()... The saving grace is that when I set the debug level to INFO, the problem goes away... Am copy/pasting the relevent stacktrace...I have also debugged this on eclipse and the exact location is the call to "new Printer(....)" in AbstractFlushingEventListener.java java.util.ConcurrentModificationException 10:07:28,421 INFO [STDOUT] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:787) 10:07:28,421 INFO [STDOUT] at java.util.HashMap$ValueIterator.next(HashMap.java:817) 10:07:28,421 INFO [STDOUT] at org.hibernate.pretty.Printer.toString(Printer.java:90) 10:07:28,421 INFO [STDOUT] at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:97) 10:07:28,421 INFO [STDOUT] at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:954) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1099) 10:07:28,421 INFO [STDOUT] at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) PS: This is my first attempt at logging issues at JIRA. Kindly point out any deficiencies or irregularities in this attempt. -- 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, 1 month

6
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2031) Add functions to Dialect that can disable use of schema and catalog parts -- for HSQLDB support

by Brian Holmes (JIRA)

Add functions to Dialect that can disable use of schema and catalog parts -- for HSQLDB support ----------------------------------------------------------------------------------------------- Key: HHH-2031 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2031 Project: Hibernate3 Type: Patch Components: core Versions: 3.1.3 Environment: This patch is against r9668 of /tags/v313/Hibernate3. Reporter: Brian Holmes Attachments: hibernate3-v313-support_schema_catalog_names.patch HSQLDB does not support the use of three part names, that is Tables with schema and catalog parts. This patch adds two functions to Dialect: supportsSchemaNames() and supportsCatalogNames(). Table.getQualifiedName() checks these values to decide whether to use or ignore the schema and catalog parts. By default these are enabled in Dialect. This patch only disables their use in HSQLDialect. This change is necessary for people who normally use Schema and Catalog names for access their primary database, but also use HSQLDB for Unit Testing. Without it, HSQLDB is unusable for Unit Testing because it fails on use of any catalog or schema names. -- 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
3
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-2308) Adjusting the Outer Join Predicate using Criteria Query

by Ben Grant (JIRA)

Adjusting the Outer Join Predicate using Criteria Query ------------------------------------------------------- Key: HHH-2308 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2308 Project: Hibernate3 Type: New Feature Components: query-criteria Versions: 3.2.1 Environment: Linux Using MS SQLServer Reporter: Ben Grant I have two tables Table A ||Col_1||Col_2|| |London| UK | |Liverpool| UK | | New York | USA | Table B ||Col_1||Col_2|| Col_3|| | UK | Europe | 0 | USA | Americas | 1 Using the Criteria class, Restriction Class and FetchMode, Hibernate manages to create a query that looks like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 where TableB3_.Col_3=1 When really i need the query to be like this select distinct top 2000 this_.Col_1 as y0_, TableB3_.Col2 as y1_ from TableA this_ left outer join TableB TableB3_ on this_.Col_2= TableB3_.Col_1 AND TableB3_.Col_3=1 currently their isn't any know way for hibernate to adjust or apply filters within the join clause. -- 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

12
27
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2007