October 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6734) Small performance improvement in ActionQueue.clear()

by Sanne Grinovero (JIRA)

Small performance improvement in ActionQueue.clear() ---------------------------------------------------- Key: HHH-6734 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6734 Project: Hibernate Core Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (OGM-93) Upgrade to Hibernate Search 4.0.0.Beta2

by Sanne Grinovero (JIRA)

Upgrade to Hibernate Search 4.0.0.Beta2 --------------------------------------- Key: OGM-93 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-93 Project: Hibernate OGM Issue Type: Improvement Components: query Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.0-next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[Hibernate-JIRA] Created: (OGM-94) JTATransactionManagerTransaction is using a new logger in each instance

by Sanne Grinovero (JIRA)

JTATransactionManagerTransaction is using a new logger in each instance ----------------------------------------------------------------------- Key: OGM-94 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-94 Project: Hibernate OGM Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero It's not a critical issue, but is creating a performance bottleneck. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (OGM-92) Migrate logging to JBoss Logging

by Emmanuel Bernard (JIRA)

Migrate logging to JBoss Logging -------------------------------- Key: OGM-92 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-92 Project: Hibernate OGM Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Today we use SLF4J but we should migrate to JBoss Logging like code does and use the type-safe approach. The idea is to do it in two steps: - add the type-safe JBoss Logging infrastructure - convert the logs proper If someone in the community could at least do the first step, that would be awesome :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6731) Improve PutFromLoadValidatorUnitTestCase to be less timesensitive

by Strong Liu (JIRA)

Improve PutFromLoadValidatorUnitTestCase to be less timesensitive ----------------------------------------------------------------- Key: HHH-6731 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6731 Project: Hibernate Core Issue Type: Improvement Components: testsuite Reporter: Strong Liu Assignee: Galder Zamarreno Priority: Minor org.hibernate.test.cache.infinispan.access.PutFromLoadValidatorUnitTestCase will often fail on the CI machines as they are very slow. I'm going to improve the test. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HV-519) Typos in ValidationMessages_de.properties

by Hardy Ferentschik (JIRA)

Typos in ValidationMessages_de.properties ----------------------------------------- Key: HV-519 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-519 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 4.2.0.Final Reporter: Hardy Ferentschik Priority: Minor Fix For: 4.3.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HBX-1193) reverse engineering of UniqueConstraint annotation for function-based indexes

by Steve Maring (JIRA)

reverse engineering of UniqueConstraint annotation for function-based indexes ----------------------------------------------------------------------------- Key: HBX-1193 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1193 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.4.GA Reporter: Steve Maring getting a runtime error ... [code]org.hibernate.AnnotationException: Unable to create unique key constraint (SYS_NC00048$) on table WRKR: SYS_NC00048$ not found[/code] the generated entity looks like this: [code]@Entity @Table(name="WRKR" , uniqueConstraints = { @UniqueConstraint(columnNames="SYS_NC00048$"), @UniqueConstraint(columnNames="SYS_NC00047$"), @UniqueConstraint(columnNames="LOGIN_VAL"), @UniqueConstraint(columnNames="SOCL_SECUR_NUM_VAL"), @UniqueConstraint(columnNames="AD_LOGIN_VAL")} ) public class Wrkr implements java.io.Serializable {[/code] Interesting thing is that this data seems to be coming from the table Indexes. They read ... [code] Index Name Uniqueness Index Type Columns Column Expression IX_WRKR_01 UNIQUE NORMAL WRKR_SEQ IX_WRKR_12 UNIQUE NORMAL SOCL_SECUR_NUM_VAL IX_WRKR_16 UNIQUE FUNCTION-BASED NORMAL SYS_NC00047$ UPPER("AD_LOGIN_VAL") IX_WRKR_17 UNIQUE FUNCTION-BASED NORMAL SYS_NC00048$ UPPER("LOGIN_VAL") IX_WRKR_UQ_LOGIN_VAL UNIQUE NORMAL LOGIN_VAL IX_WRKR_UQ_AD_LOGIN_VAL UNIQUE NORMAL AD_LOGIN_VAL [/code] WRKR_SEQ is the primary key, and SOCL_SECUR_NUM_VAL, LOGIN_VAL, and AD_LOGIN_VAL are "real" columns. The other two SYS_NC0004#$ are not actual columns in the table. They seem to be some sort of "function-based" Oracle indexes/columns that you only see in the list of indexes. tried: <table name="WRKR"> <column name="SYS_NC00047$" exclude="true"/> <column name="SYS_NC00048$" exclude="true"/> </table> but it didn't help. The problem seems to be isolated to the annotation generation. I would venture to say that it should NOT be generating @UniqueConstraint entries for columns that don't actually exist in the table. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
5
0 / 0

[Hibernate-JIRA] Created: (OGM-88) Move to Hibernate Core 4

by Emmanuel Bernard (JIRA)

Move to Hibernate Core 4 ------------------------ Key: OGM-88 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-88 Project: Hibernate OGM Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Fix For: 3.0-next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1423) ParameterParser bug - ordinal parameter mismatch

by Strong Liu (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1423?page=c... ] Strong Liu resolved HHH-1423. ----------------------------- Resolution: Out of Date I think this is fixed in 4.0, please give it a try, if it doesn't, then please create a new one, link this to the new one, and a test case please thanks > ParameterParser bug - ordinal parameter mismatch > ------------------------------------------------- > > Key: HHH-1423 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1423 > Project: Hibernate Core > Issue Type: Bug > Components: query-hql > Affects Versions: 3.1.2 > Environment: Windows XP SP2, JDK 1.5.0_06-b05, Spring 1.2.6, antlr-2.7.6rc1 > Reporter: Artur Wronski > Assignee: Strong Liu > Priority: Critical > Attachments: HHH1423Test.java, ParameterParser.2.patch, ParameterParser.3.patch, ParameterParser.patch, RecognizerBug.java > > > There is still problem with ParameterParser. The same was in Hibernate 3.1.1 > Runnable TestCase in attachment. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3133) ParameterParser incorrectly identifies positional paramters as output parameters

by Michael Cervantes (JIRA)

ParameterParser incorrectly identifies positional paramters as output parameters -------------------------------------------------------------------------------- Key: HHH-3133 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3133 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Reporter: Michael Cervantes Any HQL that references a property with the text "call" in it will throw off the parser. For instance: <i>FROM Cdr WHERE account.id = ? AND callStart >= ? AND callStart < ?</i> kept giving me ordinal parameter errors because "callStart" tricks the parser into thinking there's an output parameter. -- 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, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2011