May 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3291) Hibernate QueryStatistics should permit keying by Named Query nickname when available

by Jim Doyle (JIRA)

Hibernate QueryStatistics should permit keying by Named Query nickname when available ------------------------------------------------------------------------------------- Key: HHH-3291 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3291 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.2.x Environment: JBoss 4.2.2 Reporter: Jim Doyle This request is related to the additional feature request HHH3289 for show_sql. QueryStatistics are keyed by the full HQL query string. For monitoring and tuning persistence tier performance in midsize to large applications, it is more convenient to store the Named Query name rather than the full HQL such that the application developers can locate the named query in their annotated core, or in orm.xml, and make the changes needed to conduct performance tuning. I propose changing the mechanism that deposits query statistics: use the Query Name for Named JPQL/HQL and Named Native Queries prefix ad hoc native SQL queries with 'native;" and use that as the statistics key use the existing HQL query string for all ad hoc HQL queries -- 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

17 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3290) Hibernate Statistics getExecutionMinTime() always returns 0

by Jim Doyle (JIRA)

Hibernate Statistics getExecutionMinTime() always returns 0 ----------------------------------------------------------- Key: HHH-3290 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3290 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.1 Environment: JBoss 4.2.2.GA Reporter: Jim Doyle Priority: Minor Attachments: hibernateStats.jsp The minimum exec time is initialized to Zero but is never updated propertly to reflect the true minimum measured query time. This should be easy to fix: Either set the MinTime = Long.MAX_VALUE , or, set the MinTime=CurrentQueryTime only for the first measurement sample. Here's some sample output: A portable JSP for dumping the hibernate statistics is provided. You will need to edit the ObjectName to reflect the name of the Hibernate statistics JMX Object in your implementation. -- 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

17 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3289) show_sql output should identify the Named Query associated with generated SQL output

by Jim Doyle (JIRA)

show_sql output should identify the Named Query associated with generated SQL output ------------------------------------------------------------------------------------ Key: HHH-3289 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3289 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.3.0 Reporter: Jim Doyle It is useful to know which named query was at cause for generated SQL traffic in output logs. Medium sized applications can realistically employ a hundred named queries and it is extremely useful to known the ID of the named query as well as see the generated SQL. This feature would very much improve the ability of DBAs to undertake performance tuning. In a typical use case, the DBA would cut and paste the generated show_sql query directly in the the vendor database Explain tool to analyze performance. After manually tuning the query in the Explain analyzer, changes to the JPQL or HQL can then be applied, deployed and tested again by looking at the generated SQL. I propose changing the show_sql output to appear as follows: 10:21:04,397 INFO [STDOUT] Hibernate [MYsessionFactoryId] [MYnamedQueryName] : select top 5 pro0_.transactionID as transact2_27_, pro0_.date as date27_, pro0_.suffix_suffixCodeID as suffix40_27_, pro0_.creationDate as creation4_27_, .... A String that identifies the Session Factory will be printed to disambiguate the originating SF that produced the SQL. This is necessary in environments where more than one session factory is present (JBoss container, multiply deployed application in Tomcat). In such cases, it *MIGHT* be possible for two different session factories to have identically named named queries, so by printing an Id for the Session Factory, there is a means of resolving this when examing the output. The Named Query identifier will only appear for Named Native or Named JPQL/HQL type queries. For ad-hoc queries, the brackets may be either empty or not present to indicate that the generated SQL verbs originate from a source other than a named query. -- 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

17 years, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-197) Move to slf4j

by Emmanuel Bernard (JIRA)

Move to slf4j ------------- Key: HSEARCH-197 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-197 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.0 -- 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

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (EJB-359) Move to slf4j

by Emmanuel Bernard (JIRA)

Move to slf4j ------------- Key: EJB-359 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-359 Project: Hibernate Entity Manager Issue Type: Improvement Components: EntityManager Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.4.0.CR1 -- 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

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-57) Move to slf4j

by Emmanuel Bernard (JIRA)

Move to slf4j ------------- Key: HV-57 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-57 Project: Hibernate Validator Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.0.CR1 -- 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

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-741) Move to slf4j

by Emmanuel Bernard (JIRA)

Move to slf4j ------------- Key: ANN-741 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-741 Project: Hibernate Annotations Issue Type: Improvement Components: binder Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.4.0.CR1 -- 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

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3288) CallableStatement problem...callable not yet supported for native queries

by Thomas Modeneis (JIRA)

CallableStatement problem...callable not yet supported for native queries ------------------------------------------------------------------------- Key: HHH-3288 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3288 Project: Hibernate3 Issue Type: New Feature Components: query-sql Environment: java Reporter: Thomas Modeneis Priority: Blocker Attachments: hibernate.rar when i try to execute some insert as attachement: procedure.txt some error "callable not yet supported for native queries" occours. what can i do to execute this query ? Regards, Thomas. -- 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

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3287) Provide access to protected values of DatasourceConnectionProvider for HEM

by Emmanuel Bernard (JIRA)

Provide access to protected values of DatasourceConnectionProvider for HEM -------------------------------------------------------------------------- Key: HHH-3287 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3287 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.3.0.CR1 Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.3.0.CR2 -- 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

17 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-879) Enable joining the same association twice with Criteria

by Davide Magni (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-879?page=co... ] Davide Magni commented on HHH-879: ---------------------------------- Hi, is there any planning on fixing this bug? We have to work with very complex Object and DB where Criteria query would be very useful. > Enable joining the same association twice with Criteria > ------------------------------------------------------- > > Key: HHH-879 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-879 > Project: Hibernate3 > Issue Type: Improvement > Components: core > Reporter: Vladimir Bayanov > > Make double joining the same association with Criteria.createCriteria possible. See: http://forum.hibernate.org/viewtopic.php?t=931249 -- 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

17 years, 11 months

1
0
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 May 2008