September 2012 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-6005) DefaultComponentSafeNamingStrategy breaks @ElementCollection of @Embeddables

by Artem Troitskiy (JIRA)

DefaultComponentSafeNamingStrategy breaks @ElementCollection of @Embeddables ---------------------------------------------------------------------------- Key: HHH-6005 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6005 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Reporter: Artem Troitskiy Priority: Minor {{DefaultComponentSafeNamingStrategy}} is incompatible with {{@ElementCollection}} of {{@Embeddable}} objects. Given the following classes {code:java} @Entity public class Foo { @ElementCollection private List<Bar> bars; ... } @Embeddable public class Bar { private String name; ... } {code} and DefaultComponentSafeNamingStrategy as a naming strategy, Hibernate generates the schema with the following incorrect table: bq. create table Foo_bars (Foo_id bigint not null, bars_collection&&element_name varchar(255)) {{.collection&&element.}} is an internal placeholder that should be removed before use of property name. Other naming strategies effectively remove it by using the part of property name after the last {{.}}, but {{DefaultComponentSafeNamingStrategy}} doesn't, it just replaces {{.}} with {{_}}. Here is a workaround: {code:java} public class FixedDefaultComponentSafeNamingStrategy extends DefaultComponentSafeNamingStrategy { @Override public String propertyToColumnName(String propertyName) { return super.propertyToColumnName(propertyName.replace(".collection&&element.", ".")); } } {code} -- 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, 3 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5138) Redesign types and introduce TypeRegistry

by Steve Ebersole (JIRA)

Redesign types and introduce TypeRegistry ----------------------------------------- Key: HHH-5138 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5138 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 Work in progress. The general idea is to have 3 levels of types: 1) What I am tentatively calling a StaticType. These are basic mappings between standard java types and basic sql types. They require no access to a Session nor SessionFactory to fulfill their contracts. 2) Scoped. This is mainly the current Type contract, except that these will be explicitly scoped to a TypeRegistry (which is part of the Configuration and SessionFactory). Users can provide overrides of these. 3) User types. Again, mainly the current user types contracts. -- 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, 3 months

5
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1101) How would Faceting and geolocation work?

by Emmanuel Bernard (JIRA)

How would Faceting and geolocation work? ---------------------------------------- Key: HSEARCH-1101 URL: https://hibernate.onjira.com/browse/HSEARCH-1101 Project: Hibernate Search Issue Type: New Feature Components: query, spatial Reporter: Emmanuel Bernard Fix For: spatial How would people do faceting per location? ElasticSearch has that and it seems like a good idea. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-78) Incorrect fields are ignored by projection: an exception should be raised

by Emmanuel Bernard (JIRA)

Incorrect fields are ignored by projection: an exception should be raised ------------------------------------------------------------------------- Key: HSEARCH-78 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-78 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.0.beta3 Reporter: Emmanuel Bernard Priority: Minor -- 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, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-943) Consolidate tests against more database dialects

by Sanne Grinovero (JIRA)

Consolidate tests against more database dialects ------------------------------------------------ Key: HSEARCH-943 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-943 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.CR1 >From the different databases in QA labs we have reports like "SQLGrammarException: Invalid object name 'Cloud'." for mssql2008R1 and some other small changes needed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-1097) upgrade required jars as many are old and marked as beta

by austin collins (JIRA)

upgrade required jars as many are old and marked as beta -------------------------------------------------------- Key: HSEARCH-1097 URL: https://hibernate.onjira.com/browse/HSEARCH-1097 Project: Hibernate Search Issue Type: Improvement Affects Versions: 4.1.0.Final Reporter: austin collins i notice many of the required jars packaged in hibernate search 4.1 up are quite old now and some of them are beta. it would be good to clean this up and move away from beta jars. in particular i refer to snappy and apis -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
16
0 / 0

[Hibernate-JIRA] Created: (HV-295) Apply constraints on the elements of an iterator

by Emmanuel Bernard (JIRA)

Apply constraints on the elements of an iterator ------------------------------------------------ Key: HV-295 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-295 Project: Hibernate Validator Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik The use case is the ability to ask a constraint to be applied, not on the annotated element itself but on the elements contained by the annotated element (typically an Iterator). Hardy and I have been discussing various options. I will list them in various comments -- 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, 3 months

5
32
0 / 0

[Hibernate-JIRA] Created: (HHH-7207) SQLServer2005Dialect.insertRowNumberFunction() is broken for field names containing "from"

by Holger Pretzsch (JIRA)

SQLServer2005Dialect.insertRowNumberFunction() is broken for field names containing "from" ------------------------------------------------------------------------------------------ Key: HHH-7207 URL: https://hibernate.onjira.com/browse/HHH-7207 Project: Hibernate ORM Issue Type: Bug Components: query-sql Affects Versions: 4.1.1 Environment: Hibernate 4.1.1, Microsoft SQL Reporter: Holger Pretzsch The Microsoft SQL 2005 and 2008 dialects, which are both based on SQLServer2005Dialect, create broken queries when the entities involved have a mapped column with a name containing "from". This is evidently happens because of the implementation of the dialect's insertRowNumberFunction() method {code} protected void insertRowNumberFunction(StringBuilder sql, CharSequence orderby) { // Find the end of the select statement int selectEndIndex = sql.indexOf( FROM ); // Insert after the select statement the row_number() function: sql.insert( selectEndIndex - 1, ", ROW_NUMBER() OVER (" + orderby + ") as __hibernate_row_nr__" ); } {code} which searches the entire query string for the string "from" and inserts the given string at the first occurance. This will break queries if "from" appears as a column name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5209) org.hibernate.hql.ast.QuerySyntaxException when running a JPQL query with a MEMBER OF on an @ElementCollection

by Pascal Thivent (JIRA)

org.hibernate.hql.ast.QuerySyntaxException when running a JPQL query with a MEMBER OF on an @ElementCollection -------------------------------------------------------------------------------------------------------------- Key: HHH-5209 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5209 Project: Hibernate Core Issue Type: Bug Components: core, entity-manager Affects Versions: 3.5.1 Environment: Hibernate EM 3.5.1, HSQLDB, Derby, H2 Reporter: Pascal Thivent Priority: Blocker Attachments: QueryTest.patch I have an entity with an attribute of type {{Set<String>}} annotated as {{@ElementCollection}}. Running a query with a {{MEMBER OF}} on this attribute fails with Hibernate (but works with the RI): {code} select user from User user where :role member of user.roles {code} This is valid JPQL but Hibernate is not able to generate the corresponding SQL properly: {code:java} java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: unexpected end of subtree [select user from org.hibernate.ejb.test.User user where :role member of user.roles] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1222) at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1168) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:271) at org.hibernate.ejb.test.query.QueryTest.testMemberOfElementCollection(QueryTest.java:110) 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 junit.framework.TestCase.runTest(TestCase.java:154) at org.hibernate.test.annotations.HibernateTestCase.runTest(HibernateTestCase.java:95) at org.hibernate.test.annotations.HibernateTestCase.runBare(HibernateTestCase.java:83) at org.hibernate.ejb.test.TestCase.runBare(TestCase.java:224) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: org.hibernate.hql.ast.QuerySyntaxException: unexpected end of subtree [select user from org.hibernate.ejb.test.User user where :role member of user.roles] at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:54) at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:47) at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:82) at org.hibernate.hql.ast.QueryTranslatorImpl.generate(QueryTranslatorImpl.java:244) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:205) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:98) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1761) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:268) ... 19 more {code} I'm not sure this would be the right place (this seems to be a problem in Hibernate Core actually) but I've implemented a test method in {{org.hibernate.ejb.test.query.QueryTest}} demonstrating the problem. The patch is 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

12 years, 3 months

5
15
0 / 0

[Hibernate-JIRA] Created: (OGM-104) Document transaction isolation behaviour of Infinispan

by Sanne Grinovero (JIRA)

Document transaction isolation behaviour of Infinispan ------------------------------------------------------ Key: OGM-104 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-104 Project: Hibernate OGM Issue Type: Task 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, 3 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2012