February 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-136) CachingWrapperFilter does not cache

by Tobias Hill (JIRA)

CachingWrapperFilter does not cache ------------------------------------ Key: HSEARCH-136 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-136 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Tobias Hill See http://forum.hibernate.org/viewtopic.php?p=2369054#2369054 The CachingWrapperFilter uses the reader instance as a key for the caching. In HibernateSearch readers seems to be wrapped into a MultiReader which by itself is new each time and thus defeat the cache purpose. -- 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

18 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-147) Allow projection of Lucene DocId

by Christian Wiedmann (JIRA)

Allow projection of Lucene DocId -------------------------------- Key: HSEARCH-147 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-147 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.0.0.GA Reporter: Christian Wiedmann Priority: Minor It would be nice if the Lucene docid could be projected from a query so that TokenSources.getAnyTokenStream(IndexReader reader, int docId, String field, Analyzer analyzer) can be used. This function has the advantage that it extracts the token stream from Lucene without reparsing if it is able to. If it is unable, it will reparse the stored field with the given analyzer. -- 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

18 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1830) Error during parse query on MS SQL

by Wadi Ernesto Jalil Maluf (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1830?page=c... ] Wadi Ernesto Jalil Maluf commented on HHH-1830: ----------------------------------------------- Hi All, I'm having the same problem, I would like to know if it's related with the anotations or not, so I could have a workaround. May I do something to speed up things? May be someone can point me where to look on the code?I need to fix ASAP so if there is anything I can do, please feel free to contact me, Thanks in advance, Regards, Wadi > Error during parse query on MS SQL > ---------------------------------- > > Key: HHH-1830 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1830 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.1.2, 3.2.0.cr2 > Environment: Microsoft SQL Server 2000, Windows XP, JDK 1.5 Update 4 > Reporter: Den Raskovalov > Priority: Critical > Attachments: hibernateBug.tar.gz > > > HQL: select deal, items.dateBegin, client.Title from " + CoreDeal.class.getName() + " deal left join deal.stagesWorkflowInstance.history.items items, " + CoreClient.class.getName() + " client where stageResponsible=:stageResponsible and items.index=maxindex(items) and deal.parent=client and deal.stagesWorkflowInstance.Stage.showOnPersonalPage=1 > It works normally on Oracle, but on MS SQL produces: > Error: String index out of range: -5 > [java.lang.StringIndexOutOfBoundsException] > java.lang.String.substring(String.java:1768) > java.lang.String.substring(String.java:1735) > org.hibernate.hql.CollectionSubqueryFactory.createCollectionSubquery(CollectionSubqueryFactory.java:32) > org.hibernate.hql.ast.tree.FromElementType.toColumns(FromElementType.java:301) > org.hibernate.hql.ast.tree.FromElementType.toColumns(FromElementType.java:291) > org.hibernate.hql.ast.tree.FromElement.toColumns(FromElement.java:377) > org.hibernate.hql.ast.tree.MethodNode.resolveCollectionProperty(MethodNode.java:115) > org.hibernate.hql.ast.tree.MethodNode.collectionProperty(MethodNode.java:95) > org.hibernate.hql.ast.tree.MethodNode.resolve(MethodNode.java:44) > org.hibernate.hql.ast.HqlSqlWalker.processFunction(HqlSqlWalker.java:844) > org.hibernate.hql.antlr.HqlSqlBaseWalker.functionCall(HqlSqlBaseWalker.java:2324) > org.hibernate.hql.antlr.HqlSqlBaseWalker.expr(HqlSqlBaseWalker.java:1285) > org.hibernate.hql.antlr.HqlSqlBaseWalker.exprOrSubquery(HqlSqlBaseWalker.java:4032) > org.hibernate.hql.antlr.HqlSqlBaseWalker.comparisonExpr(HqlSqlBaseWalker.java:3521) > org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1758) > org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1686) > org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1683) > org.hibernate.hql.antlr.HqlSqlBaseWalker.logicalExpr(HqlSqlBaseWalker.java:1683) > org.hibernate.hql.antlr.HqlSqlBaseWalker.whereClause(HqlSqlBaseWalker.java:776) > org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:577) > org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) > org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) > org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:227) > org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:159) > org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:110) > org.hibernate.engine.query.HQLQueryPlan.(HQLQueryPlan.java:77) > org.hibernate.engine.query.HQLQueryPlan.(HQLQueryPlan.java:56) > org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:71) > org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) > org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) > org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1612) > ru.naumen.crm2.bobjects.deal.CoreDealHibernateHandler.listAllDealsWithSortDataByResponsible(CoreDealHibernateHandler.java:109) > ru.naumen.crm2.ui.tlc.CoreEmployeeTableListController.listMyDealsSorted(CoreEmployeeTableListController.java:70) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-125) Add support for fields declared by interface or unmapped superclass

by Igor Stroh (JIRA)

Add support for fields declared by interface or unmapped superclass ------------------------------------------------------------------- Key: HSEARCH-125 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-125 Project: Hibernate Search Issue Type: Improvement Components: engine, mapping Affects Versions: 3.0.0.GA Reporter: Igor Stroh Priority: Minor Attachments: IndexedTarget.patch If an @IndexedEmbedded field is delcared by an interface or a unmapped superclass, there is no way hibernate-search can resolve the concrete class (compare to org.hibernate.annotations.Target or the targetEntity parameter for @*To* annotations). The attached patch solves this issue by introducing a IndexedTarget annotation which, much like @Target, expects the mapped class as its single parameter. See test/org/hibernate/search/test/embedded/ changes for a simple example. This issue was first exmplained in http://forum.hibernate.org/viewtopic.php?p=2366118 -- 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

18 years, 1 month

3
6
0 / 0

[Hibernate-JIRA] Created: (EJB-335) Polymorphic delete fails while creating a temp table

by Heiko W. Rupp (JIRA)

Polymorphic delete fails while creating a temp table ---------------------------------------------------- Key: EJB-335 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-335 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.2.1 Environment: Postgres 8.3, hibernate hibernate 3.2 from rev 14201 Reporter: Heiko W. Rupp We have an Entity @Entity @Inheritance(strategy = InheritanceType.TABLE_PER_CLASS) MeasurementData { @EmbeddedId MeasurementDataPK id; @JoinColumn(name = "SCHEDULE_ID", insertable = false, updatable = false) @ManyToOne(fetch = FetchType.LAZY) Schedule schedule; .. } and Subclasses: MeasurementDataNum(_1h,_6h,..) extends MeasurementData { Double value; } MeasurementDataTrait extends MeasurementData { String value; } A bulk delete "DELETE FROM MeasurementData md WHERE md.schedule IN (:schedules ) " fails with Caused by: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not insert/select ids for bulk delete at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:629) at org.hibernate.ejb.QueryImpl.executeUpdate(QueryImpl.java:57) Postgres 8.3 complains about the following SQL: ERROR: UNION types double precision and character varying cannot be matched insert into HT_MeasurementData select measuremen0_.TIME_STAMP as TIME_STAMP, measuremen0_.SCHEDULE_ID as SCHEDULE_ID from ( select value, maxvalue, SCHEDULE_ID, TIME_STAMP, minvalue, 1 as clazz_ from MEASUREMENT_DATA_NUM_1D union all select value, maxvalue, SCHEDULE_ID, TIME_STAMP, minvalue, 2 as clazz_ from MEASUREMENT_DATA_NUM_1H union all select value, maxvalue, SCHEDULE_ID, TIME_STAMP, minvalue, 3 as clazz_ from MEASUREMENT_DATA_NUM_6H union all select value, null::float8 as maxvalue, SCHEDULE_ID, TIME_STAMP, null::float8 as minvalue, 4 as clazz_ from RHQ_MEASUREMENT_DATA_TRAIT ) measuremen0_ where SCHEDULE_ID in ($1 , $2 , $3) So basically it creates a column for "value" and tries to insert strings and doubles into it. The "obvious" :-) solution would be only to insert the timestamp and schedule id into the table and not the value and other stuff that is not needed to identify the items to delete. -- 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

18 years, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3104) Using a Constructor in the select clause causes additional selects

by Heiko W. Rupp (JIRA)

Using a Constructor in the select clause causes additional selects ------------------------------------------------------------------ Key: HHH-3104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3104 Project: Hibernate3 Issue Type: Bug Environment: hibernate 3.2 from rev 14201, Postgres 8.3 Reporter: Heiko W. Rupp We have JPA Queries in the form "SELECT new Foo(e1, e2.scalar) FROM Entity1 e1 JOIN e1.entity2 e2 WHERE ..." When I do a Query.getResultList() on this, I end up with n+1 Selects for n rows: - 1 query for the scalar - n queries for each instance of Entity1 that should be returned. If I do "SELECT new Foo(e1,e2) .." I even end up with 2 selects per row: 1 for each e1 and one for each e2. If I do "SELECT e1, e2 FROM Entity1 e1 JOIN e1.entity2 e2 WHERE ..." I end up with one select only . -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3103) move to java.util.ConcurrentHashMap for EntityModeToTuplizerMapping with move to JDK5

by Steve Ebersole (JIRA)

move to java.util.ConcurrentHashMap for EntityModeToTuplizerMapping with move to JDK5 ------------------------------------------------------------------------------------- Key: HHH-3103 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3103 Project: Hibernate3 Issue Type: Sub-task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.x See HHH-2645 for the discussion -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3101) HQL "is not true" gets incorrectly changed into SQL "<>true"

by Gertjan van Oosten (JIRA)

HQL "is not true" gets incorrectly changed into SQL "<>true" ------------------------------------------------------------ Key: HHH-3101 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3101 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.6, 3.2.5 Environment: PostgreSQL Reporter: Gertjan van Oosten Priority: Minor An HQL query with a where-clause on a boolean field like this: where boolValue is not true [boolValue is of type boolean, possibly NULL] which, according to the SQL:2003 standard and PostgreSQL's implementation thereof, means: select all rows that have a boolValue of either UNKNOWN (or NULL) or FALSE. However, this HQL statement gets translated into SQL like this: where sometable0_.bool_value<>true which is semantically different: select all rows that have a bool_value of FALSE, thus missing all rows where bool_value is UNKNOWN (or NULL). -- 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

18 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-130) Should provide better log infos (on the indexBase parameter for the FSDirectoryProvider)

by Eric Perrocheau (JIRA)

Should provide better log infos (on the indexBase parameter for the FSDirectoryProvider) ---------------------------------------------------------------------------------------- Key: HSEARCH-130 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-130 Project: Hibernate Search Issue Type: Improvement Components: directory provider Affects Versions: 3.0.0.GA Reporter: Eric Perrocheau Priority: Minor When tracking bugs due to invalid directories names for the FSDirectoryProvider, it could be nice if the logs did inform more on Hibernate Search behaviour, or help highlight some problem. E.g., if the indexes already exist on disk, under windows vista, and we provide the directory name with erroneous trailing spaces in the configuration file : Hibernate Search run half well : the only problem is that it clears the old indexes on initializing the FSDirectoryProvider since it didn't find the directory with the trailing spaces. After that, it doesn't seem to mind the wrong directory name since it finds and uses the good one. Is suppose we could expect Hibernate Search to tell that something is happening and why, in fact, without having to go in the code with the debugger to find that the trailing spaces are sometimes a problem and sometimes not. (this improvement was asked for on http://forum.hibernate.org/viewtopic.php?t=980567 ) -- 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

18 years, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-126) Better diagnostic when Search index directory cannot be opened

by Ian (JIRA)

Better diagnostic when Search index directory cannot be opened -------------------------------------------------------------- Key: HSEARCH-126 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-126 Project: Hibernate Search Issue Type: Patch Affects Versions: 3.1.0 Environment: Found in version deployed inside JBoss-Seam 2.0.0.CR2, but affects more Reporter: Ian Priority: Minor Attachments: DirectoryProviderHelper.diff When Search cannot create the index directory, the message in the Exception thrown by o.h.s.util.DirectoryProviderHelper.java contains the path as entered by the original user; it is often the case that this will be deployed inside an application server and the user will not know the correct path that is in need of permissions repair because of the way e.g., JBoss-AS creates randomly named subdirectories under e.g., server/default/deploy. This just changes the message to include the full path if the user gave an absolute path. -- 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

18 years, 1 month

2
5
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 February 2008