March 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-305) Hibernate search doesn't work with criteria when it is not initialized laziily

by prabhu lal (JIRA)

Hibernate search doesn't work with criteria when it is not initialized laziily ------------------------------------------------------------------------------ Key: HSEARCH-305 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-305 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.0.1.GA Environment: MYSQL,HIBERNATE 3.0 , Flex with dpHibernate Reporter: prabhu lal Attachments: QueryLoader.java For the RIA applications complete object tree should be initialized(To achieve that there is work around available like dpHibernate). But hibernate search doesn't apply criteria to queried result because it returns the result on the basis of wether objectt is intialized by loading the criteria objects.Since there is no lazy intiaialization so all the objects are loaded andcomplete result will be return irrespctive of criteria. code snipet from Hibernate Search API(org.hibernate.search.engine.QueryLoader.java.): public List load(EntityInfo... entityInfos) { final int maxResults = entityInfos.length; if ( maxResults == 0 ) return EMPTY_LIST; if ( entityType == null ) throw new AssertionFailure( "EntityType not defined" ); if ( criteria == null ) criteria = session.createCriteria( entityType ); DocumentBuilder builder = searchFactoryImplementor.getDocumentBuilders().get( entityType ); String idName = builder.getIdentifierName(); int loop = maxResults / MAX_IN_CLAUSE; boolean exact = maxResults % MAX_IN_CLAUSE == 0; if ( !exact ) loop++; Disjunction disjunction = Restrictions.disjunction(); for (int index = 0; index < loop; index++) { int max = index * MAX_IN_CLAUSE + MAX_IN_CLAUSE <= maxResults ? index * MAX_IN_CLAUSE + MAX_IN_CLAUSE : maxResults; List ids = new ArrayList( max - index * MAX_IN_CLAUSE ); for (int entityInfoIndex = index * MAX_IN_CLAUSE; entityInfoIndex < max; entityInfoIndex++) { ids.add( entityInfos[entityInfoIndex].id ); } disjunction.add( Restrictions.in( idName, ids ) ); } criteria.add( disjunction ); criteria.list(); //load all objects //mandatory to keep the same ordering List result = new ArrayList( entityInfos.length ); for (EntityInfo entityInfo : entityInfos) { Object element = session.load( entityInfo.clazz, entityInfo.id ); if ( Hibernate.isInitialized( element ) ) { //This is true for all the objects,in case objects are eagrly intialized //all existing elements should have been loaded by the query, //the other ones are missing ones result.add( element ); } } return result; } -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-337) Search return the same row multiple times on Select

by Santhosh Kumaran (JIRA)

Search return the same row multiple times on Select --------------------------------------------------- Key: HSEARCH-337 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-337 Project: Hibernate Search Issue Type: Bug Environment: Hibernate Reporter: Santhosh Kumaran I have a table in the following pattern on MySQL 5.1 Table1 Key1 int Key2 int field1 tinyint field2 tinyint field3 tinyint I have the sql query like "SELECT {table1Entity.*} FROM TABLE1 table1 where Key1=?" This query will satify for 3 rows and has to get me the 3 filtered rows. and the code like this SQLQuery sqlQuery = session.createSQLQuery(query); sqlQuery.setInteger(0, 5001); sqlQuery = sqlQuery.addEntity("table1Entity", Table1Entity.class); List entityList = sqlQuery.list(); The list contain 3 entity objects, but 3 copies of the first row. ( not all 3 rows). First row coming 3 times instead of 2nd and 3rd row values. Please let me know, is it a bug or not? - SANSSAN -- 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

14 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-341) Support for fetch joins in Hibernate search queries

by Seema Richard (JIRA)

Support for fetch joins in Hibernate search queries --------------------------------------------------- Key: HSEARCH-341 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-341 Project: Hibernate Search Issue Type: New Feature Components: query Affects Versions: 3.1.0.GA Reporter: Seema Richard In Hibernate search, the related entities marked using @IndexedEmbedded are now getting lazy fetched which is causing unnecessary queries to be generated. It would be useful if fetch joins can be used for better performance. -- 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

14 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-350) @IndexedEmbedded appears to handle only declared type, not subtypes

by Taylor Mathewson (JIRA)

@IndexedEmbedded appears to handle only declared type, not subtypes ------------------------------------------------------------------- Key: HSEARCH-350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-350 Project: Hibernate Search Issue Type: Improvement Components: mapping Reporter: Taylor Mathewson Given the following: @Indexed class A{ @IndexedEmbedded public B b; } class B{ ...//some indexed fields } public class C{ ...//some more indexed fields } The index for A will only contain the indexed fields in B, never the fields in C, even if the runtime type of A's b property is of class C. Thank you. -- 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

14 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-313) Provide a callback on indexing exception

by Emmanuel Bernard (JIRA)

Provide a callback on indexing exception ---------------------------------------- Key: HSEARCH-313 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-313 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard An application can pass a callback and be notified when an indexing operation fails. The data associated with the operation is passed as a parameter (eg list of lucene work). The application can do anything from here: - log failing ids - swallow - put that in a queue for retry etc -- 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

14 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-351) Index fields on subclasses of a field marked @IndexEmbedded

by Dimas Guardado, Jr. (JIRA)

Index fields on subclasses of a field marked @IndexEmbedded ----------------------------------------------------------- Key: HSEARCH-351 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-351 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.1.0.GA Reporter: Dimas Guardado, Jr. the fields of the subclasses of a property marked with @IndexedEmbedded are not getting indexed, but the fields of the base class are. I discussed this issue previously on the forums, and I was directed to file a JIRA issue for it. For more context and a code example to illustrate the problem, please see the following forum thread: http://forum.hibernate.org/viewtopic.php?p=2404209#2404209 -- 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

14 years, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3449) Unable to use Oracle stored procedure in a <sql-query>

by RC (JIRA)

Unable to use Oracle stored procedure in a <sql-query> ------------------------------------------------------ Key: HHH-3449 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3449 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.6 Environment: Hibernate 3.2.6GA Oracle 10.2.0.4 (& Oracle JDBC Driver version - 11.1.0.6.0) Java 1.6.0_06 Reporter: RC Using a stored procedure to fetch result set. However, an IllegalAccessException is thrown: Caused by: org.hibernate.HibernateException: Problem while trying to load or access OracleTypes.CURSOR value at org.hibernate.dialect.Oracle8iDialect.registerResultSetOutParameter(Oracle8iDialect.java:371) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1560) at org.hibernate.loader.Loader.doQuery(Loader.java:673) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2213) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.custom.CustomLoader.list(CustomLoader.java:289) at org.hibernate.impl.SessionImpl.listCustomQuery(SessionImpl.java:1695) at org.hibernate.impl.AbstractSessionImpl.list(AbstractSessionImpl.java:142) at org.hibernate.impl.SQLQueryImpl.list(SQLQueryImpl.java:152) at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:811) .... Caused by: java.lang.IllegalAccessException: Class org.hibernate.dialect.Oracle8iDialect can not access a member of class oracle.jdbc.driver.OracleTypes with modifiers "" at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) at java.lang.Class.newInstance0(Class.java:349) at java.lang.Class.newInstance(Class.java:308) at org.hibernate.dialect.Oracle8iDialect.registerResultSetOutParameter(Oracle8iDialect.java:369) ... 35 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

14 years, 9 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3395) Oracle LONG datatype fetching fails on superclass Criteria query

by Ville Anttonen (JIRA)

Oracle LONG datatype fetching fails on superclass Criteria query ---------------------------------------------------------------- Key: HHH-3395 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3395 Project: Hibernate3 Issue Type: Bug Environment: Oracle 10 Windows XP Hibernate 3 Weblogic 9.2 Reporter: Ville Anttonen I have dao-layer method like this. public PersistentQuery getPersistentQuery(String userId, long queryId){ .... Criteria criteria = m_session.createCriteria(PersistentQuery.class); criteria.add(Expression.eq("userId",userId)); criteria.add(Expression.eq("id",new Long(queryId))); return (PersistentQuery) criteria.uniqueResult(); ..... } Previous code throws "Stream already closed" exception. PersistentQuery is abstract class and it's subclasses contains UserType - field that wraps Oracle's long varchar field. I can fix this by creating criteria by subclass like " Criteria criteria = m_session.createCriteria(PersistentOrganizationQuery.class); ". We're migrating from ingres -> oracle and in ingres previous implementation worked fine. -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3406) IndexOutOfBoundsException when a flush occurs during validation inside a flush

by vincent Larchet (JIRA)

IndexOutOfBoundsException when a flush occurs during validation inside a flush ------------------------------------------------------------------------------ Key: HHH-3406 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3406 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: 3.2.6ga, oracle11g, tomcat 6.0.16, spring 2.5.1, redhat5.2 or windows XP or debian etch Reporter: vincent Larchet Say we have entity A: @Entity public class A { [...] @AssertTrue public boolean validateSomeCondition(){ //call service S B=S.loadEntityB() [.... do some stuff with B...] } } In my hibernate session I modifiy several entities among them A1, A2, A3 (instances of A), then I flush the session that firsts validates A1. Inside A1.validateSomeCondition() I have to call a service that loads some data inside its own transaction, thus when it returns a commit is triggered that is intercepted an hibernate flushes its session, and not only entities bound to this transaction but the WHOLE session (including A2, A3 !!!). Then validation of A1 finishes successfully and A1 is saved to db, but right after that this exception occurs java.lang.IndexOutOfBoundsException: Index: 1, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.springframework.orm.hibernate3.HibernateTransactionManager.doCommit(HibernateTransactionManager.java:596) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:709) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:678) at org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:319) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:116) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) [...] I do not really know if flushing A2,A3 entites inside the 2nd flush is an issue or not (I do not mind actually...), so I suggest this quick fix: inside ActionQueue method private void executeActions(List list) throws HibernateException { int size = list.size(); for(int i = 0; i < size; i++) execute((Executable)list.get(i)); list.clear(); session.getBatcher().executeBatch(); } replace the "static" int size = list.size(); for(int i = 0; i < size; i++) by an iterator... thx vincent NB: we use OpenSessionInViewFilter -- 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

14 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-352) Introduce a programmatic mapping API

by Emmanuel Bernard (JIRA)

Introduce a programmatic mapping API ------------------------------------ Key: HSEARCH-352 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-352 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.2.0 Initial commit. A lot of work to do still. The core idea is here but we need to: - complete the API describing the mapping - complete its binding to annotations - support merge between the programmatic API and annotations PS: if we go all the way for that, we won't have people nagging for XML support anymore :) -- 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

14 years, 9 months

1
10
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2009