December 2008 - 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, 8 months

2
1
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, 8 months

2
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, 8 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, 8 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-318) Extend IndexWriterSetting to include a flag indicating whether it makes sense to have different settings for batch and index

by Hardy Ferentschik (JIRA)

Extend IndexWriterSetting to include a flag indicating whether it makes sense to have different settings for batch and index ---------------------------------------------------------------------------------------------------------------------------- Key: HSEARCH-318 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-318 Project: Hibernate Search Issue Type: Bug Components: engine Reporter: Hardy Ferentschik Fix For: 3.1.1 Not sure whether IndexWriterSetting is the right place to do this, but I think it could work. This issue relates to HSEARCH-298. -- 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
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2088) TypeMismatchException on object equality expression from one-to-one relationship

by Salvatore Insalaco (JIRA)

TypeMismatchException on object equality expression from one-to-one relationship -------------------------------------------------------------------------------- Key: HHH-2088 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2088 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Reporter: Salvatore Insalaco Suppose to have entity A with a one-to-one constrained relationship to an entity B, called bRel. The query: "from A a, B b where a.bRel = b" raises a TypeMismatchException, even if bRel and b are instances of the same entity. This happens because in BinaryLogicOperatorNode: - lhsType is org.hibernate.type.Type = org.hibernate.type.OneToOneType(B)", with getColumnSpan returning 0. - rhsType is org.hibernate.type.Type = org.hibernate.type.ManyToOneType(B)", with getColumnSpan returning 1. And it compares the two columnspans. It doesn't happen with 3.2.0.cr2. -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-322) Review MultiClassesQueryLoader

by Hardy Ferentschik (JIRA)

Review MultiClassesQueryLoader ------------------------------ Key: HSEARCH-322 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-322 Project: Hibernate Search Issue Type: Task Components: engine Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.1.1 review MultiClassesQueryLoader (and write unit tests?) This task got created after talking with Sanne about MultiClassesQueryLoader. -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3586) SequenceHiLoGenerator generates values ahead of the actual sequence

by Krasimir Chobantonov (JIRA)

SequenceHiLoGenerator generates values ahead of the actual sequence ------------------------------------------------------------------- Key: HHH-3586 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3586 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1, Oracle 10G Reporter: Krasimir Chobantonov The code that needs to be change in on line 83 of the SequenceHiLoGenerator here is the line hi = hival * ( maxLo+1 ); basically we should add (+) the maxLo +1 to the current sequence value represented bu the hival instead of using multiply (*) -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2679) One to Many Unidirectional Association using Join Tables and <list> causes duplicate key constraint violation when an entry is deleted from the list.

by Priyajeet Hora (JIRA)

One to Many Unidirectional Association using Join Tables and <list> causes duplicate key constraint violation when an entry is deleted from the list. ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2679 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2679 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Java 1.5, Hibernate 3.2, MySQL 5. Might also effect NHibernate similarly. Reporter: Priyajeet Hora Priority: Critical Consider this unidirectional one-to-many relation done using join tables. Person --> Address (*). The hibernate mapping is pretty much the same as http://www.hibernate.org/hib_docs/v3/reference/en/html/associations.html#... Though I am using <list> rather than a <set> Following is the DDL (presented roughly) created by the hbm2ddl tool. Table PersonAddress Person_id varcahr not null Address_id varchar not null unique Person_list_index integer not null primary key (Person_id, Person_list_index) I create a person1 - person_id=1. I create add1, add2, add3 - address_id=2,3,4 respectively. then I add all 3 addresses to the list in person1. persist it to database. all good. At this point in the database -- person_id---person_list_index---address_id 1--0--2 1--1--3 1--2--4 I get person1 back. I remove add1. save person1 back. CONSTRIANT VIOLATION HERE DUE TO DUPLICATE KEY. looking at what hibernate does ... So after 1st save and before remove this is whats in the database - person_id---person_list_index---address_id 1--0--2 1--1--3 1--2--4 basically shows the one to many there. I want to remove the record no. 1--0--2. That is the 1st one. So with the 1st row gone, hibernate needs to shift other records up so that the new list index is assingned. expected output---- 1--0--3 1--1--4 This is how hibernate proceeds Step1: save info and delete on 1--2--4, to get rid of that last record. Step2: update 1--0--2 to 1--0--3 BANG...CONSTRAINT VIOLATION DUE TO DUPLICATE KEY. Why? because "3" in that address_id column is already there and that column is "unique" according to DDL. Step3: update 1--0--3 to info saved from step1, that is to 1--1--4. But cant persist this since step 2 fails. Basically the algorithm of copy the value up when a delete is performed is not doing the copy correctly. Way to get around this is to remove the "unique" constrint, but then that makes the relation a many to many. ----------------------------------------------------------------------------- CREATE TABLE `PERSON` ( `PRESON_ID` varchar(255) NOT NULL, PRIMARY KEY (PRESON_ID) ) CREATE TABLE `ADDRESS` ( `ADDRESS_ID` varchar(255) NOT NULL, PRIMARY KEY (ADDRESS_ID) ) CREATE TABLE `PERSONADDRESS` ( `PERSON_ID` varchar(255) NOT NULL , `PERSON_IDX` integer NOT NULL , `ADDRESS_ID` varchar(255) NOT NULL UNIQUE, PRIMARY KEY (PERSON_ID, PERSON_IDX) ) ALTER TABLE `PERSONADDRESS` ADD INDEX `PERSONADDRESS_FK_PERSON` (`PERSON_ID`), ADD CONSTRAINT `PERSONADDRESS_FK_PERSON` FOREIGN KEY (`PERSON_ID`) REFERENCES PERSON(`PERSON_ID`) ALTER TABLE `PERSONADDRESS` ADD INDEX `PERSONADDRESS_FK_ADDRESS` (`ADDRESS_ID`), ADD CONSTRAINT `PERSONADDRESS_FK_ADDRESS` FOREIGN KEY (`ADDRESS_ID`) REFERENCES ADDRESS(`ADDRESS_ID`) Person.hbm.xml ------------------------- <list name="AddressList" lazy="false" table="PersonAddress"> <key column="PERSON_ID" /> <index column="PERSON_IDX" /> <many-to-many column="ADDRESS_ID" unique="true" class="Address" /> </list> Address.hbm.xml -------------------------- No information about Person, since this is a unidirectional association. Target doesnt know about the source. Test psuedocode ------------------------- //start transaction Person person = new Person(); Address add1 = new Address(); Address add2 = new Address(); Address add3 = new Address(); person.add(add1); person.add(add2); person.add(add3); // persist to database person.save // end transaction // start transaction // get back that person from database person.remove(add1); // persist to database person.save <<<<<<<<<<<<<<< FAILS, duplicate key constraint violation // end transaction -- 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
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2008