April 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-809) Composite Key which contains a discriminator causes "Repeated Column" errors

by Pasi Orovuo (JIRA)

Composite Key which contains a discriminator causes "Repeated Column" errors ---------------------------------------------------------------------------- Key: ANN-809 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-809 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate version: 3.3.1 GA Application Server: Glassfish V3 Prelude Database: Oracle 9i Reporter: Pasi Orovuo Attachments: ItemInfo.zip See this forum post for background: http://forum.hibernate.org/viewtopic.php?t=995693 Annotations does not seem to have a possibility to define "insert = false" on a discriminator column, as mentioned in the following bug: http://opensource.atlassian.com/projects/hibernate/browse/HB-1149 Sources of classes that demonstrate the problem in above forum case attached. -- 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

13 years, 10 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6849) SQLServer2005Dialect changes the order of selected columns when using pagination

by Hardy Ferentschik (JIRA)

SQLServer2005Dialect changes the order of selected columns when using pagination -------------------------------------------------------------------------------- Key: HHH-6849 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6849 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR6 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.next The _SQLServer2005Dialect_ uses _ROW_NUMBER()_ to generate a limit string. However, it prepend the row number column instead of appending it (or not returning it at all). This let for example _PaginationTest#testLimitOffset_ fail. See also HHH-2655. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HV-484) Refactor package organisaton to clearly separate spi, public and private APIs

by Hardy Ferentschik (JIRA)

Refactor package organisaton to clearly separate spi, public and private APIs ----------------------------------------------------------------------------- Key: HV-484 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-484 Project: Hibernate Validator Issue Type: Task Components: engine Affects Versions: 4.1.0.CR1 Reporter: Hardy Ferentschik Fix For: 4.x Aligning with the other Hibernate projects. -- 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

13 years, 10 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-6310) SQLServer2005Dialect produced select statement with a distinct keyword within an aggregate function does not work

by Yoryos Valotassios (JIRA)

SQLServer2005Dialect produced select statement with a distinct keyword within an aggregate function does not work ----------------------------------------------------------------------------------------------------------------- Key: HHH-6310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6310 Project: Hibernate Core Issue Type: Bug Components: core, query-sql Affects Versions: 3.6.5 Reporter: Yoryos Valotassios As discussed on HHH-5715, the SQLServer2005Dialect does not handle the right the distinct keyword when that is inside an aggregate 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

13 years, 11 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6728) SQLServer2005Dialect - Paging doesn't work with UPPERCASE colums in a case sensitive database

by Andrei Zaitsev (JIRA)

SQLServer2005Dialect - Paging doesn't work with UPPERCASE colums in a case sensitive database --------------------------------------------------------------------------------------------- Key: HHH-6728 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6728 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR4, 3.6.7 Environment: MS SQL Server 2008 with Latin1_General_CS_AS collation Reporter: Andrei Zaitsev SQLServer2005Dialect changes the original query in getLimitString() to lowercase. That leads to SQLGrammarExcepton with case sensitive collation and not-lowercase table and column names. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-7198) SQLServer2005Dialect.getLimitString turns tablenames to lowercase -> SQLGrammarException: when mapping tables with capital letters

by Guenther Demetz (JIRA)

SQLServer2005Dialect.getLimitString turns tablenames to lowercase -> SQLGrammarException: when mapping tables with capital letters ----------------------------------------------------------------------------------------------------------------------------------- Key: HHH-7198 URL: https://hibernate.onjira.com/browse/HHH-7198 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.1.1 Environment: Hibernate4, SQLServer2008 Reporter: Guenther Demetz Priority: Minor Usually when annotating entity classes without the @Table.name attribute, then the default mapped tablenames begin with a capital letter. When using the paging feature, SQLServer2005Dialect.getLimitString turns the whole sql to lowercase {code:title=SQLServer2005Dialect.java|borderStyle=solid} @Override public String getLimitString(String querySqlString, boolean hasOffset) { StringBuilder sb = new StringBuilder(querySqlString.trim().toLowerCase()); ... return sb.toString(); } {code} thus also the included tablenames are all converted to lowercase, this leads to following schema mismatch exception, when using the original SQLServerDriver: org.hibernate.exception.SQLGrammarException: Invalid object name 'mytable' This bug was introduced with HHH-2655 (ROW_NUMBER for Paging). Testcase: {code} Query query = session.createQuery("from C"); // C is an arbitrary entity class mapped to a table with uppercase characters in the tablename query.setMaxResults(10); query.iterate().next(); // -> Exception {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
12
0 / 0

[Hibernate-JIRA] Created: (OGM-165) Add support for the SafeMode

by Guillaume Scheibel (JIRA)

Add support for the SafeMode ---------------------------- Key: OGM-165 URL: https://hibernate.onjira.com/browse/OGM-165 Project: Hibernate OGM Issue Type: New Feature Components: datastore Affects Versions: mongodb Reporter: Guillaume Scheibel Priority: Minor Use the org.hibernate.ogm.safemode (= true | false | no set) Should we provide more options to support Majority and Fsync_safe modes as well ? Here is there a description of each mode http://www.littlelostmanuals.com/2011/11/overview-of-basic-mongodb-java-w... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6960) NullPointerException in PreCollectionRemove Listener

by Kevin Jordan (JIRA)

NullPointerException in PreCollectionRemove Listener ---------------------------------------------------- Key: HHH-6960 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6960 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 4.0.0.Final Environment: Hibernate 4.0.0 to MySQL Reporter: Kevin Jordan I'm getting a NullPointerException on line 47 of EnversPreCollectionRemoveEventListenerImpl very consistently. I wasn't sure if it was due to lazy collections or not, but it seems that it fails if they're eagerly fetched or lazily fetched. I'm guessing it has something to do with getLoadedPersister() returning a null value since the comments for it say "This is only available late during the flush cycle". The stack trace is Quote: java.lang.NullPointerException at org.hibernate.envers.event.EnversPreCollectionRemoveEventListenerImpl.onPreRemoveCollection(EnversPreCollectionRemoveEventListenerImpl.java:47) at org.hibernate.action.internal.CollectionRemoveAction.preRemove(CollectionRemoveAction.java:143) at org.hibernate.action.internal.CollectionRemoveAction.execute(CollectionRemoveAction.java:104) at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:273) at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:265) at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:188) at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:323) at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:52) at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1081) at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:315) at org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.beforeTransactionCommit(JdbcTransaction.java:101) at org.hibernate.engine.transaction.spi.AbstractTransactionImpl.commit(AbstractTransactionImpl.java:175) at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:73) ... 120 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

12
39
0 / 0

[Hibernate-JIRA] Created: (HHH-6962) java.util.zip.ZipException: error in opening zip file

by Jakub Białek (JIRA)

java.util.zip.ZipException: error in opening zip file ----------------------------------------------------- Key: HHH-6962 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6962 Project: Hibernate ORM Issue Type: Bug Components: entity-manager Affects Versions: 3.6.9 Environment: hibernate 3.6.9, spring 3.0.7.RELEASE, jboss 5.1, java 1.6.0_30 (sun), debian 64 bit Reporter: Jakub Białek Priority: Minor After moving from hibernate 3.6.8 to 3.6.9 below stacktrace has appeared in logs when application is deployed: {code} WARN [org.hibernate.ejb.packaging.FileZippedJarVisitor] (HDScanner) Unable to find file (ignored): vfszip:/srv/jboss-5.1.0.GA/server/debugprfile/deploy/mywar.war/WEB-INF/lib/domain.jar/ java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:127) at java.util.jar.JarFile.<init>(JarFile.java:135) at java.util.jar.JarFile.<init>(JarFile.java:72) at org.hibernate.ejb.packaging.FileZippedJarVisitor.doProcessElements(FileZippedJarVisitor.java:65) at org.hibernate.ejb.packaging.AbstractJarVisitor.getMatchingEntries(AbstractJarVisitor.java:146) at org.hibernate.ejb.packaging.NativeScanner.getFilesInJar(NativeScanner.java:192) at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:497) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:851) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:594) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225) ...... {code} Application deploys correctly but this error didn't appear in 3.6.8. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-7107) org.hibernate.test.locking.LockModeTest hangs on Sybase 15.5 and DB2-97

by Zbyněk Roubalík (JIRA)

org.hibernate.test.locking.LockModeTest hangs on Sybase 15.5 and DB2-97 ----------------------------------------------------------------------- Key: HHH-7107 URL: https://hibernate.onjira.com/browse/HHH-7107 Project: Hibernate ORM Issue Type: Bug Affects Versions: 4.0.1 Environment: Hibernate 4.0.1.Final-redhat-1, Sybase 15.5, DB2-97 Reporter: Zbyněk Roubalík When running Hibernate testsuite on Sybase 15.5 and DB2-97, it hangs in org.hibernate.test.locking.LockModeTest. Mostly testQuery() or testLoading() test. It is new test in 4.0.1 (HHH-5275). Red Hat internal lab: https://hudson.qa.jboss.com/hudson/view/Hibernate/view/Hibernate%20QA/job... https://hudson.qa.jboss.com/hudson/view/Hibernate/view/Hibernate%20QA/job... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
7
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 April 2012