December 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3572) Create versioned entities groups

by Adam Warski (JIRA)

Create versioned entities groups -------------------------------- Key: HHH-3572 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3572 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136878 Each group would have its own versions table. This could speed up the system when there are a lot of versioned entities, as the versions tables would be less contested. However, if two versioned entities are connected by a (versioned) relation, they would have to be in the same group. So groups could minimally be strongly connected components of the relations graphs. -- 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

15 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5767) Add running test information to Infinispan 2LC build

by Galder Zamarreno (JIRA)

Add running test information to Infinispan 2LC build ---------------------------------------------------- Key: HHH-5767 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5767 Project: Hibernate Core Issue Type: Task Components: build Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.Alpha1 Add some logging to Infinispan gradle build to show tests being executed, i.e. test { afterTest { desc, result -> println "Executing test ${desc.name} [${desc.className}] with result: ${result.resultType}" } } -- 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

15 years, 1 month

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2460) Multiple object creates on HQL select causes "unexpected token: ,"

by Steve Mayhew (JIRA)

Multiple object creates on HQL select causes "unexpected token: ," ------------------------------------------------------------------ Key: HHH-2460 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2460 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.1.2 Environment: MySQL Reporter: Steve Mayhew When executing this query: select new java.lang.String('test1'), new java.lang.String('test2') from SomeMappedClass You get a syntax error. It does not matter what is in the from clause, result is always the same. [2007-03-01 16:51:29,349] [ERROR:org.hibernate.hql.PARSER] [] - line 1:37: unexpected token: , [2007-03-01 16:51:29,365] [DEBUG:org.hibernate.hql.ast.AST] [] - --- HQL AST --- \-[QUERY] 'query' org.hibernate.hql.ast.QuerySyntaxException: unexpected token: , near line 1, column 37 [select new java.lang.String('test1'), new java.lang.String('test2') from SomeMappedClass at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:59) at org.hibernate.hql.ast.QueryTranslatorImpl.parse(QueryTranslatorImpl.java:244) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:155) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:109) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:75) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:54) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:71) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:134) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:113) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1602) at net.jvnet.dev.hqe.ThreadHQLQueryExecution.run(Unknown Source) Caused by: line 1:37: unexpected token: , at org.hibernate.hql.antlr.HqlBaseParser.selectFrom(HqlBaseParser.java:1145) at org.hibernate.hql.antlr.HqlBaseParser.queryRule(HqlBaseParser.java:702) at org.hibernate.hql.antlr.HqlBaseParser.selectStatement(HqlBaseParser.java:296) at org.hibernate.hql.antlr.HqlBaseParser.statement(HqlBaseParser.java:159) at org.hibernate.hql.ast.QueryTranslatorImpl.parse(QueryTranslatorImpl.java:238) ... 9 more -- 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

15 years, 1 month

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5590) Don't log and rethrow exceptions in AbstractFlushingEventListener

by Gregg (JIRA)

Don't log and rethrow exceptions in AbstractFlushingEventListener ----------------------------------------------------------------- Key: HHH-5590 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5590 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0.CR1, 3.5.6, 3.3.2 Environment: Hibernate 3.3.2.GA Oracle Database 10.1.0.4.0 JDK 1.6.0_17 Reporter: Gregg Priority: Trivial Attachments: AbstractFlushingEventListener.patch For a similar issue covering logging-and-rethrowing overall, see http://opensource.atlassian.com/projects/hibernate/browse/HB-1308. This issue covers a specific instance in order to minimize the impact on the codebase. However, I would be all for elimination of every instance of log-and-rethrow in the codebase. In this particular instance, I have a table A with a foreign key referencing records in table B. In my user interface, I give the user the ability to delete records from table B. If the user attempts to delete a record from table B that is referred to in table A, the database throws an integrity constraint violation. This exception is caught in AbstractFlushingEventListener.performExecutions, logged, and rethrown. My code sees the exception and informs the user that the record cannot be deleted because it's already in use in the system. So the exception ends up showing up in my logs (from the log.error() statement in AbstractFlushingEventListener.performExecutions) even though I'm handling it properly. I would like the log.error() statement removed since the code propagates the exception. Attached is a patchfile. I'm not including a test case because I feel the issue is so simplistic that one isn't necessary. -- 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

15 years, 1 month

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5615) Switch to JBoss logging

by Steve Ebersole (JIRA)

Switch to JBoss logging ----------------------- Key: HHH-5615 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5615 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 org.jboss.logging:jboss-logging -- 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

15 years, 1 month

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3494) HQLQueryPlan gives back zero result for "getSingleResult()" although one result is available

by Christian Hofschroer (JIRA)

HQLQueryPlan gives back zero result for "getSingleResult()" although one result is available -------------------------------------------------------------------------------------------- Key: HHH-3494 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3494 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.1 Environment: 3.3.1.GA, hsqldb 1.8.0.7 Reporter: Christian Hofschroer Attachments: patch.txt I have run the following code snippets both and only the second one works, because there is a bug in HQLQueryPlan. // This does not work correctly (query is javax.persistence.Query) ExampleObject e = (ExampleObject) query.getSingleResult(); // Replacement with this code works List l=query.getResultList() ; assertEquals(1,l.size()) ; ExampleObject e=(ExampleObject)l.get(0) ; This problem occurs only in seldom cases when 1. Hibernate executes several sql queries and merges the result and 2. There is a limit of results (the limit is "2" in version 3.3.1.GA, because only one result is expected anyway) Attached is a patch for the class HQLQueryPlan. The line if ( distinction.add( result ) ) { has to be replaced with if ( ! distinction.add( result ) ) { In case the object was found it returns "true". With the current implementation the object is not added to "combinedResults" although it should be added. It was not possible to reproduce the problem with the setup from "testsuite". If necessary I can provide a JUnit testcase. -- 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

15 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5766) New services are not wired into standalone SchemaExport, SchemaUpdate, and SchemaValidator

by Gail Badner (JIRA)

New services are not wired into standalone SchemaExport, SchemaUpdate, and SchemaValidator ------------------------------------------------------------------------------------------ Key: HHH-5766 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5766 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Assignee: Gail Badner Fix For: 4.0.0.Alpha1 -- 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

15 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-360) DefaultTraversableResolver.isReachable() should be enhanced to return true for validations with group other than Default

by Georges-Etienne Legendre (JIRA)

DefaultTraversableResolver.isReachable() should be enhanced to return true for validations with group other than Default ------------------------------------------------------------------------------------------------------------------------ Key: HV-360 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-360 Project: Hibernate Validator Issue Type: Improvement Affects Versions: 4.1.0.Final Reporter: Georges-Etienne Legendre Assignee: Hardy Ferentschik We use Bean Validator to validate transition between domain object states. We use groups to allow different validations for each state. When we want to change the state of an object, we get the object from the database (using JPA). However, because we use LAZY loading, only the loaded beans get validated. This causes problems because nothing is in fact validated (other than the first bean of course). I know the JSR tells that the default TraversableResolver should verify if JPA is in the classpath. However, this doesn't make sense when groups are used for the purpose described above. There are 2 workarounds: * Disable LAZY loading! * Implement a TraversableResolver that returns true for isReachable() However, I'm wondering if the DefaultTraversableResolver.isReachable() can be enhanced to return true for validations with group other than Default. -- 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

15 years, 1 month

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3571) Change the default revision entity configuration

by Adam Warski (JIRA)

Change the default revision entity configuration ------------------------------------------------ Key: HHH-3571 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3571 Project: Hibernate Core Issue Type: Task Components: envers Reporter: Adam Warski Assignee: Adam Warski Fix For: 3.4 The current revision table and field names are not accepted by databases such as Oracle. Hence: - change the revision entity name from _revision_entity to something acceptable by all databases (REVISION_ENTITY?) - change the revision field name from _revision (to revision?) Also, change the default id generation strategy from native to org.hibernate.id.enhanced.SequenceStyleGenerator Document those changes in the manual with a migration note! -- 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

15 years, 1 month

3
12
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-531) Use Lucene fieldcache

by Sanne Grinovero (JIRA)

Use Lucene fieldcache --------------------- Key: HSEARCH-531 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-531 Project: Hibernate Search Issue Type: Improvement Components: query Reporter: Sanne Grinovero Fix For: 3.4.0 The Lucene per-segment FieldCache should be used for strings we fetch from the index (Stored), by default as we do with classname and PK. It might be useful for people to be able to add more fields to this cache in case of projections usage. (It's purpose is to speed up this reading of stored info - being per segment it's not invalidated per new IndexReader but per changed segments). Likely need a switch to turn it off, as it could consume much memory. -- 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

15 years, 1 month

1
4
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 December 2010