May 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-7327) Caching access type should be determined using AccessType.fromExternalName(cacheElement.getUsage())

by Gail Badner (JIRA)

Caching access type should be determined using AccessType.fromExternalName(cacheElement.getUsage()) --------------------------------------------------------------------------------------------------- Key: HHH-7327 URL: https://hibernate.onjira.com/browse/HHH-7327 Project: Hibernate ORM Issue Type: Bug Components: metamodel Reporter: Gail Badner Assignee: Gail Badner Fix For: 5.0.0 HBM XML uses lower-case values for access type, which is not recognized using AccessType.valueOf(). Instead AccessType.fromExternalName(cacheElement.getUsage()) should be used. -- 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-7326) Determine if collection key is nullable or updateable

by Gail Badner (JIRA)

Determine if collection key is nullable or updateable ----------------------------------------------------- Key: HHH-7326 URL: https://hibernate.onjira.com/browse/HHH-7326 Project: Hibernate ORM Issue Type: Task Components: metamodel Reporter: Gail Badner Fix For: 5.0.0 Determine if collection key is nullable or updateable. >From the documentation: not-null (optional): specifies that the foreign key columns are not nullable. This is implied whenever the foreign key is also part of the primary key. -- 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: (HHH-7325) Allow disabling XML validations via setting

by Steve Ebersole (JIRA)

Allow disabling XML validations via setting ------------------------------------------- Key: HHH-7325 URL: https://hibernate.onjira.com/browse/HHH-7325 Project: Hibernate ORM Issue Type: Bug Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 5.0.0 Allow disabling XML validations via setting -- 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-181) Rework EntityKeyBuilder (Remove a method called "getColumnMap")

by Seiya Kawashima (JIRA)

Rework EntityKeyBuilder (Remove a method called "getColumnMap") --------------------------------------------------------------- Key: OGM-181 URL: https://hibernate.onjira.com/browse/OGM-181 Project: Hibernate OGM Issue Type: Sub-task Reporter: Seiya Kawashima Assignee: Seiya Kawashima To make Voldemort work with hibernate OGM, the implementation adds a method in EntityKeyBuilder called getColumnMap to get column names when fields use different names as its column names. The mapping seems required to deserialize JSON to an object with the correct type. However, it' not necessary to be there and also it only returns one column name as String which is not right. Rework EntityKeyBuilder to remove the method. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2828) criteria search by class throws org.hibernate.QueryException: Unsupported discriminator type null when mapping exists for this class

by jo desmet (JIRA)

criteria search by class throws org.hibernate.QueryException: Unsupported discriminator type null when mapping exists for this class ------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2828 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2828 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: hibernate 3.2.5, oracle 10g Reporter: jo desmet Attachments: src.zip when making a criteria based on a property of type class the query succeeds if this class is not mapped, the query building fails when this class is mapped within hibernate and has no discriminator e.g. code : Criteria l = session.createCriteria(SearchClass.class); l.add(Restrictions.eq("type", ClassWithNoMapping.class)); // SUCCESS java.util.List result = l.list(); l = session.createCriteria(SearchClass.class); l.add(Restrictions.eq("type", ClassWithMapping.class)); // EXCEPTION result = l.list(); exception is Hibernate: select this_.ID as ID0_0_, this_.name as name0_0_, this_.type as type0_0_ from SEARCHCLASS this_ where this_.type=? org.hibernate.QueryException: Unsupported discriminator type null at org.hibernate.loader.criteria.CriteriaQueryTranslator.getTypedValue(CriteriaQueryTranslator.java:499) at org.hibernate.criterion.SimpleExpression.getTypedValues(SimpleExpression.java:71) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getQueryParameters(CriteriaQueryTranslator.java:251) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:95) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1569) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) at Test.list(Test.java:40) at Test.main(Test.java:27) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) classes are attached, tables should exists but no data is required. Please also provide workaround on short term if possible -- 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, 8 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-7324) Add support for SERIAL columns in SapDB (MaxDB) dialect

by Adam Dyga (JIRA)

Add support for SERIAL columns in SapDB (MaxDB) dialect ------------------------------------------------------- Key: HHH-7324 URL: https://hibernate.onjira.com/browse/HHH-7324 Project: Hibernate ORM Issue Type: Improvement Components: core Affects Versions: 3.6.10 Reporter: Adam Dyga Priority: Minor Currently org.hibernate.dialect.SAPDBDialect doesn't support SERIAL columns. The code below shows how how to do it by subclassing SAPDBDialect but it could be included in SAPDBDialect directly... {code} /** * Extends SAPDBDialect to support identity (serial) columns in MaxDB. * * @author Adam Dyga * */ public class MaxDBDialect extends SAPDBDialect { /** * */ public MaxDBDialect() { } @Override public String getIdentitySelectString(String table, String column, int type) throws MappingException { return "select " + table + ".currval from dual"; } @Override public boolean supportsIdentityColumns() { return true; } @Override public boolean hasDataTypeInIdentityColumn() { return true; } @Override public String getIdentityColumnString(int type) throws MappingException { return "serial"; } } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-7323) SQLServerDialectTest.testMaxResultsSqlServerWithCaseSensitiveCollation fails on mssql2008R1 and mssql2008R2 due to Lock request TimeOut period exceeded

by Madhumita Sadhukhan (JIRA)

SQLServerDialectTest.testMaxResultsSqlServerWithCaseSensitiveCollation fails on mssql2008R1 and mssql2008R2 due to Lock request TimeOut period exceeded ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-7323 URL: https://hibernate.onjira.com/browse/HHH-7323 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.1.3 Reporter: Madhumita Sadhukhan Assignee: Strong Liu Refer https://issues.jboss.org/browse/JBPAPP-9041 SQLServerDialectTest.testMaxResultsSqlServerWithCaseSensitiveCollation fails on mssql2008R1 and mssql2008R2 with following stacktrace: org.hibernate.hql.internal.ast.QuerySyntaxException: Product is not mapped [from Product where description like 'Kit%'] at org.hibernate.hql.internal.ast.util.SessionFactoryHelper.requireClassPersister(SessionFactoryHelper.java:180) Query failing: * select id from Product2 with (updlock, rowlock, nowait) where id =? 08:38:09,174 WARN SqlExceptionHelper:143 - SQL Error: 1222, SQLState: S00051 08:38:09,175 ERROR SqlExceptionHelper:144 - Lock request time out period exceeded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-7322) Add support for one-to-many associations to new metamodel

by Gail Badner (JIRA)

Add support for one-to-many associations to new metamodel --------------------------------------------------------- Key: HHH-7322 URL: https://hibernate.onjira.com/browse/HHH-7322 Project: Hibernate ORM Issue Type: Task Components: metamodel Reporter: Gail Badner Assignee: Gail Badner Fix For: 5.0.0 Add support for one-to-many associations to new metamodel. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1129) Enable annotation processors automatic setup on Eclipse project import

by Sanne Grinovero (JIRA)

Enable annotation processors automatic setup on Eclipse project import ---------------------------------------------------------------------- Key: HSEARCH-1129 URL: https://hibernate.onjira.com/browse/HSEARCH-1129 Project: Hibernate Search Issue Type: Task Components: build Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 4.2 Thanks to Fred Bricon and his contributions to m2e Eclipse is now able to import the project correctly, automatically setting up annotation processing. This is a mayor step forward for Eclipse users, as Eclipse would screw up the annotation processing settings any time it would detect a dependency change, as it would require a project configuration reset performed by the plugin.. this would happen frequently when changing GIT branches. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-7321) HQL: Combining a CROSS JOIN with a LEFT JOIN which requires a WITH clause triggers an exception.

by negora (JIRA)

HQL: Combining a CROSS JOIN with a LEFT JOIN which requires a WITH clause triggers an exception. ------------------------------------------------------------------------------------------------- Key: HHH-7321 URL: https://hibernate.onjira.com/browse/HHH-7321 Project: Hibernate ORM Issue Type: Bug Components: query-hql Affects Versions: 4.1.3, 4.1.0 Environment: JDK 7.0 Update 4 JBoss AS 7.0.1 Final Reporter: negora I'm trying to combine a CROSS JOIN with a LEFT JOIN. The last one requires a WITH clause that references one of tables used in the CROSS JOIN. For example, I want to list students, questions of an exam, and their answers to them. Some answers may not exist, thus I'm using a LEFT JOIN: SELECT s.studentId, q.questionId, sa.answer FROM Student s, Question q LEFT JOIN s.studentAnswerList AS sa WITH sa.question.questionId = q.questionId This causes an exception: javax.ejb.EJBException: java.lang.IllegalArgumentException: org.hibernate.hql.internal.ast.QuerySyntaxException: with-clause referenced two different from-clause elements . The entities are really simple. These are their attributes: - Student.studentId - Question.questionId - StudentAsnwer.studentAnswerId - StudentAsnwer.studentId - StudentAsnwer.questionId - StudentAsnwer.answer I've been suffering from the same problem in both 3.x and 4.x versions of Hibernate. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2012