April 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2400) ability to specify joinType in createAlias in DetachedCriteria

by Michal Pavlasek (JIRA)

ability to specify joinType in createAlias in DetachedCriteria -------------------------------------------------------------- Key: HHH-2400 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2400 Project: Hibernate3 Type: New Feature Versions: 3.2.1 Environment: 3.2.1 Reporter: Michal Pavlasek Criteria has two methods than can create an alias, but DetachedCriteria has only one method, without the possibility of specifying the joinType. It will be very useful for me to have that opportunity. Now I have to use Criteria instead of DetachedCriteria in some cases. Criteria: Criteria createAlias(String associationPath, String alias) Join an association, assigning an alias to the joined association. Criteria createAlias(String associationPath, String alias, int joinType) Join an association using the specified join-type, assigning an alias to the joined association. DetachedCriteria: DetachedCriteria createAlias(String associationPath, String alias) -- 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, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2379) adding a new method to DetachedCriteria

by Vadim Marchenko (JIRA)

adding a new method to DetachedCriteria --------------------------------------- Key: HHH-2379 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2379 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.1 Environment: 3.2, all db flavors Reporter: Vadim Marchenko I propose to add additional method to detached criteria to allow creating of left join constructs as in public DetachedCriteria createAlias(String associationPath, String alias, int joinType) throws HibernateException { criteria.createAlias(associationPath, alias, joinType); return this; } -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2364) DetachedCriteria.getExecutableCriteria(session) does not return a new criteria each time

by Amir Pashazadeh (JIRA)

DetachedCriteria.getExecutableCriteria(session) does not return a new criteria each time ---------------------------------------------------------------------------------------- Key: HHH-2364 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2364 Project: Hibernate3 Type: Bug Components: query-criteria Versions: 3.2.1 Reporter: Amir Pashazadeh detachedCriteria.getExecutableCriteria(session) does not return a new Criteria each time; so if some projection or ... is applied on the result criteria, it will remain on next criterias. -- 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, 7 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-1991) add alias when create a subcriteria

by Jorge L. Middleton (JIRA)

add alias when create a subcriteria ----------------------------------- Key: HHH-1991 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1991 Project: Hibernate3 Type: Improvement Components: query-criteria Versions: 3.1 rc2 Environment: windows Reporter: Jorge L. Middleton Priority: Trivial Its very simple... only I noted this: public DetachedCriteria createCriteria(String associationPath, String alias) throws HibernateException { return new DetachedCriteria( impl, criteria.createCriteria(associationPath) ); } I had a problem with this method because, hibernate doesn't recognize the alias. The point is that you have to use criteria.createCriteria(associationPath, alias); -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (EJB-273) refresh() throws entity not managed exception

by Charles Canning (JIRA)

refresh() throws entity not managed exception --------------------------------------------- Key: EJB-273 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-273 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.1 Reporter: Charles Canning Priority: Critical When you call EntityManager.refresh() to reattach an entity to the entitymanager, it throws: java.lang.IllegalArgumentException: Entity not managed at org.hibernate.ejb.AbstractEntityManagerImpl.refresh(AbstractEntityManagerImpl.java:260) The code is: public void refresh(Object entity) { checkTransactionNeeded(); //adjustFlushMode(); try { if ( ! getSession().contains( entity ) ) { throw new IllegalArgumentException( "Entity not managed" ); } getSession().refresh( entity ); } catch (MappingException e) { throw new IllegalArgumentException( e.getMessage(), e ); } catch (HibernateException he) { throwPersistenceException( he ); } } It is checking if the object is already in the session - this will not allow me to reattach. If I "cast" the EM to the session delegate, refresh works fine because it doesn't contain this check. For more info, you can look at this forum topic : http://forum.hibernate.org/viewtopic.php?t=971661&start=0&postdays=0&post... -- 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, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2022) ORA-00911: invalid character when field begins with underscore

by Jerry Cattell (JIRA)

ORA-00911: invalid character when field begins with underscore -------------------------------------------------------------- Key: HHH-2022 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2022 Project: Hibernate3 Type: Bug Components: core Versions: 3.0.5, 3.1.3, 3.2.0.cr3 Environment: Hibernate 3.1.3 Oracle 10.2.0.1 Reporter: Jerry Cattell Priority: Minor Attachments: InvalidCharacterErrorCase.java, SimpleObject.hbm.xml, SimpleObject.java Hibernate is generating invalid SQL (for Oracle) for collections that are stored in fields with names that start with underscores. In this SQL: Hibernate: select _tags0_.SIMPLE_OBJECT_ID as SIMPLE1_0_, _tags0_.TAG as TAG0_ from SIMPLE_OBJECT_TAG _tags0_ where _tags0_.SIMPLE_OBJECT_ID=? an alias called "_tags0_" is created for the collection table. Unfortunately, Oracle does not allow non-alphabetic characters for the first character in an alias. Here's the stacktrace: Hibernate: select _tags0_.SIMPLE_OBJECT_ID as SIMPLE1_0_, _tags0_.TAG as TAG0_ from SIMPLE_OBJECT_TAG _tags0_ where _tags0_.SIMPLE_OBJECT_ID=? WARN JDBCExceptionReporter 20060822-011120.817 - SQL Error: 911, SQLState: 42000 ERROR JDBCExceptionReporter 20060822-011120.818 - ORA-00911: invalid character INFO DefaultLoadEventListener 20060822-011120.820 - Error performing load command org.hibernate.exception.SQLGrammarException: could not initialize a collection: [SimpleObject._tags#1] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.loadCollection(Loader.java:1926) at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:36) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1676) at org.hibernate.collection.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:454) at org.hibernate.engine.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:755) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:229) at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:47) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:41) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2730) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:365) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:346) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:161) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:862) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:799) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:792) at InvalidCharacterErrorCase.runTest(InvalidCharacterErrorCase.java:28) at InvalidCharacterErrorCase.main(InvalidCharacterErrorCase.java:11) 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:585) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) Caused by: java.sql.SQLException: ORA-00911: invalid character at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:799) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:839) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1132) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3329) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139) at org.hibernate.loader.Loader.getResultSet(Loader.java:1669) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.loadCollection(Loader.java:1919) ... 26 more I have attached a test case that causes this error. After a little bit of research, it appears that a change to StringHelper.generateAlias(String description, int unique) (or StringHelper.generateAliasRoot(String description)) to remove all characters up to the first alphabetic character would solve this problem. -- 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, 7 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-9) Add ShardAware interface and related exit strategy logic

by Nathan Silberman (JIRA)

Add ShardAware interface and related exit strategy logic -------------------------------------------------------- Key: HSHARDS-9 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-9 Project: Hibernate Shards Issue Type: New Feature Components: strategy Affects Versions: 3.0.0.Beta1 Environment: Hibernate 3.2, Database: DB2 Reporter: Nathan Silberman Assignee: Max Ross Domain model awareness of its host Shard. Any domain model that implemented a 'ShardAware' interface would contain a Set<ShardId> that could be injected by the relevant ExitStrategy. This could be solved by adding the following interface: ------------------------------------------------------- package org.hibernate.shards; import org.hibernate.shards.ShardId; import java.util.Set; /** * Interface for persistent objects that are aware of the virtual shardIds * that host them. */ public interface ShardAware { /** * Sets the virtual ShardIds that host the implementing * persistant object * * @param shardid * a non-null, non-empty Set of ShardIds * @throws IllegalArgumentException * if <tt>shardIds</tt> is null or empty */ void setShardIds( Set<ShardId> shardids ); } --------------------------------------------------- An simple exit strategy that could be used, for example, would set the ShardIds for each resulting ShardAware domain model: ------------------------------------------------------ package org.hibernate.shards.strategy.exit; import java.util.List; import org.hibernate.shards.Shard; import org.hibernate.shards.ShardAware; /** * ShardAwareConcatenateListsExistStrategy sets the ShardIds on each of the given * objects returned by each Shard. * * One should be aware that usage of this class adds O(n) overhead to each retrieval * as the setting of each ShardIds Set is invoked by iterating over the entire resultSet. */ public class ShardAwareConcatenateListsExistStrategy extends ConcatenateListsExitStrategy { @Override public synchronized boolean addResult(List<Object> oneResult, Shard shard ) { if ( oneResult != null && ! oneResult.isEmpty() && oneResult.get( 0 ) instanceof ShardAware ) { for( Object object : oneResult ) { ((ShardAware)object).setShardIds( shard.getShardIds() ); } } return super.addResult( oneResult, shard ); } } --------------------------------------- This change might require changes wherever ShardAccessStrategy.apply() could be invoked. I have made the changes including a small alteration to the ShardedCriteriaImpl, to use ShardAwareConcatenateListsExistStrategy instead of ConcatenateListsExitStrategy, with success. -- 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, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2563) Log messages in LoadContexts.locateLoadingCollectionEntry(CollectionKey key) are incorrect

by Gail Badner (JIRA)

Log messages in LoadContexts.locateLoadingCollectionEntry(CollectionKey key) are incorrect ------------------------------------------------------------------------------------------ Key: HHH-2563 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2563 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4 Environment: Hibernate3_2 branch Reporter: Gail Badner Priority: Minor Log messages should be swapped in LoadContexts.locateLoadingCollectionEntry(CollectionKey key): ... LoadingCollectionEntry rtn = ( LoadingCollectionEntry ) xrefLoadingCollectionEntries.get( key ); if ( log.isTraceEnabled() ) { if ( rtn == null ) { log.trace( "collection [" + key + "] located in load context" ); } else { log.trace( "collection [" + key + "] not located in load context" ); } } ... I'll attach a patch shortly. -- 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, 7 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HBX-826) Code generator: sortedset are not instantiated by default

by Julien Fourment (JIRA)

Code generator: sortedset are not instantiated by default ---------------------------------------------------------- Key: HBX-826 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-826 Project: Hibernate Tools Type: Bug Components: hbm2java Versions: 3.1beta3 Environment: Hibernate 3.1.3 and plus. MySQL 5.0 Reporter: Julien Fourment Priority: Minor Hi, When defining a regular (not sorted) set in an hbm file, the generated java will define the field as this: private Set<Package> packages = new HashSet<Package>(0); But when defining a sorted set in the my hbm file (using sort attribute with a comparator class) the generated java looks like this: private SortedSet<ServiceVersion> versions; Type is correct, but the field in not populated with a default implementation by default, like treeset ? I would expect something like : private SortedSet<ServiceVersion> versions = new TreeSet<ServiceVersion>(new myComparator()); -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-825) hbm2java: Circular dependency between POJO source generation and Comparator class compilation

by Julien Fourment (JIRA)

hbm2java: Circular dependency between POJO source generation and Comparator class compilation --------------------------------------------------------------------------------------------- Key: HBX-825 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-825 Project: Hibernate Tools Type: Bug Components: hbm2java Versions: 3.1beta3 Environment: Hibernate 3.1.3 and +. Using MySQL 5.0 Reporter: Julien Fourment Attachments: example_and_traces.zip Hi, My java objects are generated from the xml files using hbm2java. One of my collection is sorted using a Comparator class. hbm2java fails saying the comparator cannot be instantiated. But as the comparator makes reference to my java object, it cannot be compiled before the generation happened. We have a circular dependency here. (see example enclosed). Is there any way to fix this ? Many thanks ! -- 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, 7 months

2
3
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 April 2007