May 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-946) Add a general meta for all the tables in the database, see [HBX-575]

by Hashim Kubba (JIRA)

Add a general meta for all the tables in the database, see [HBX-575] -------------------------------------------------------------------- Key: HBX-946 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-946 Project: Hibernate Tools Issue Type: Improvement Components: reverse-engineer Affects Versions: 3.2beta9 Environment: using eclipse 3.2.2 JDK 1.5 hibernate tools 3.2beta9 h2 database ver 1.0 Reporter: Hashim Kubba Priority: Minor I'm adding meta attributes in reveng.xml (HBX-575) for customization of the resulting Java code from a reverse engineered database. yet I would really like to be able to add a general class-description to all my classes ( say @ Auther or @version ) , even better; I want all my classes to extend BasicDataObject where I can add some static final constants to use, but now I have to add that to each table <hibernate-reverse-engineering> <table name="FOO"> <meta attribute="extends">BasicDataObject</meta> </table name> <table name="BOO"> <meta attribute="extends">BasicDataObject</meta> </table name> ... </hibernate-reverse-engineering> What I would like to see is something like <hibernate-reverse-engineering> <meta attribute="extends">BasicDataObject</meta> </hibernate-reverse-engineering> and that will make all my classes extend BasicDataObject; metas that can be used directly under hibernate-reverse-engineering are: * class-description general comment for all classes * implements implements a common interface with constants * extends extends a common class with constants and common methods * scope-class make all classes protected * scope-set all sets in all classes * scope-get all gets in all classes A nice to have will be: * generated-class-suffix * generated-class-prefix or <meta name="generated-class" suffix="suffix" prefix="prefix" /> that will allow me to control all the classes names -- 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

17 years, 3 months

3
6
0 / 0

[Hibernate-JIRA] Created: (EJB-251) Incorrect SQL emitted for EJB query involving COUNT()

by Manuel Mall (JIRA)

Incorrect SQL emitted for EJB query involving COUNT() ----------------------------------------------------- Key: EJB-251 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-251 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.2.0.ga Environment: Hibernate 3.2 / MySQL 4.1.xx Reporter: Manuel Mall If you have an entity with a composite id and query it like: select count(e) from Entity e the emitted SQL looks like SELECT COUNT(e.id1, e.id2) FROM Entity However, this is at least according to MySQL invalid SQL as the COUNT function can have only one argument. -- 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

17 years, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2025) Remove log from LazyInitializationException constructor

by Russell Healy (JIRA)

Remove log from LazyInitializationException constructor ------------------------------------------------------- Key: HHH-2025 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2025 Project: Hibernate3 Type: Improvement Components: core Versions: 3.2.1 Environment: Any Reporter: Russell Healy Remove log from LazyInitializationException constructor. The motivation is to enable recovery from a LazyInitializationException using around advice without issuing a logging an error. See: http://www.jroller.com/page/cenkcivici?entry=reattaching_lazy_objects_to_... This has been asked for before [HB-1363], but is worth reconsidering. -- 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

17 years, 3 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2641) Collection Loading

by Frederico (JIRA)

Collection Loading ------------------ Key: HHH-2641 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2641 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.0 final Environment: Hibernate3, Postgresql 8.1 Reporter: Frederico Attachments: src.tar.gz I'm not sure if this is a bug, but no one answered me in the hibernate forum, so.... I have a collection that it is not loaded, in log it seems to be ok, but when i access the collection there is no element. <class name="entidades.bdufop.Sistema" table="sistema" schema="public" > <id name="codigo" column="codigo" type="java.lang.String" > <generator class="assigned"> </generator> </id> <property name="descricao" type="java.lang.String" update="true" insert="true" column="descricao" not-null="true" /> <property name="disponivel" type="java.lang.String" update="true" insert="true" column="disponivel" not-null="true" /> <property name="mensagem" type="java.lang.String" update="true" insert="true" column="mensagem" /> <set name="aplicacoes" lazy="true" cascade="all"> <key column="cod_sistema"/> <one-to-many class="entidades.bdufop.Aplicacao"/> </set> </class> <class name="entidades.bdufop.Aplicacao" table="aplicacao" schema="public" > <composite-id name="id" class="entidades.bdufop.Aplicacao_pk" > <key-property name="codigo_sistema" type="java.lang.String" column="cod_sistema" /> <key-property name="codigo_aplicacao" type="java.lang.String" column="codigo" /> </composite-id> <many-to-one name="sistema" class="entidades.bdufop.Sistema" column="cod_sistema" insert="false" update="false" unique="true" not-null="true"/> <property name="descricao" type="java.lang.String" column="descricao" not-null="true" /> <property name="versao" type="java.lang.String" column="versao" /> <property name="dt_versao" type="java.util.Date" column="dt_versao" /> <property name="disponivel" type="java.lang.String" column="disponivel" not-null="true" /> <property name="url" type="java.lang.String" column="url" /> <property name="mensagem" type="java.lang.String" column="mensagem" /> </class> Log 12:21:42,060 DEBUG DefaultInitializeCollectionEventListener:41 - initializing collection [entidades.bdufop.Sistema.aplicacoes#ACESSO] 12:21:42,063 DEBUG DefaultInitializeCollectionEventListener:47 - checking second-level cache 12:21:42,067 DEBUG DefaultInitializeCollectionEventListener:59 - collection not cached 12:21:42,071 DEBUG Loader:1911 - loading collection: [entidades.bdufop.Sistema.aplicacoes#ACESSO] 12:21:42,075 DEBUG AbstractBatcher:311 - about to open PreparedStatement (open PreparedStatements: 0, globally: 0) 12:21:42,079 DEBUG ConnectionManager:415 - opening JDBC connection 12:21:42,118 DEBUG SQL:346 - select aplicacoes0_.cod_sistema as cod1_1_, aplicacoes0_.codigo as codigo1_, aplicacoes0_.cod_sistema as cod1_1_0_, aplicacoes0_.codigo as codigo1_0_, aplicacoes0_.descricao as descricao1_0_, aplicacoes0_.versao as versao1_0_, aplicacoes0_.dt_versao as dt5_1_0_, aplicacoes0_.disponivel as disponivel1_0_, aplicacoes0_.url as url1_0_, aplicacoes0_.mensagem as mensagem1_0_ from public.aplicacao aplicacoes0_ where aplicacoes0_.cod_sistema=? Hibernate: select aplicacoes0_.cod_sistema as cod1_1_, aplicacoes0_.codigo as codigo1_, aplicacoes0_.cod_sistema as cod1_1_0_, aplicacoes0_.codigo as codigo1_0_, aplicacoes0_.descricao as descricao1_0_, aplicacoes0_.versao as versao1_0_, aplicacoes0_.dt_versao as dt5_1_0_, aplicacoes0_.disponivel as disponivel1_0_, aplicacoes0_.url as url1_0_, aplicacoes0_.mensagem as mensagem1_0_ from public.aplicacao aplicacoes0_ where aplicacoes0_.cod_sistema=? 12:21:42,122 DEBUG AbstractBatcher:424 - preparing statement 12:21:42,129 DEBUG StringType:80 - binding 'ACESSO' to parameter: 1 12:21:42,144 DEBUG AbstractBatcher:327 - about to open ResultSet (open ResultSets: 0, globally: 0) 12:21:42,148 DEBUG Loader:1040 - result set contains (possibly empty) collection: [entidades.bdufop.Sistema.aplicacoes#ACESSO] 12:21:42,152 DEBUG CollectionLoadContext:84 - uninitialized collection: initializing 12:21:42,509 DEBUG Loader:682 - processing result set 12:21:42,513 DEBUG Loader:687 - result set row: 0 12:21:42,517 DEBUG StringType:122 - returning 'ACESSO ' as column: cod1_1_0_ 12:21:42,542 DEBUG StringType:122 - returning 'AP.ACESSO ' as column: codigo1_0_ 12:21:42,550 DEBUG Loader:1164 - result row: EntityKey[entidades.bdufop.Aplicacao#component[codigo_sistema,codigo_aplicacao]{codigo_aplicacao=AP.ACESSO , codigo_sistema=ACESSO }] 12:21:42,558 DEBUG Loader:1347 - Initializing object from ResultSet: [entidades.bdufop.Aplicacao#component[codigo_sistema,codigo_aplicacao]{codigo_aplicacao=AP.ACESSO , codigo_sistema=ACESSO }] 12:21:42,563 DEBUG AbstractEntityPersister:1860 - Hydrating entity: [entidades.bdufop.Aplicacao#component[codigo_sistema,codigo_aplicacao]{codigo_aplicacao=AP.ACESSO , codigo_sistema=ACESSO }] 12:21:42,574 DEBUG StringType:122 - returning 'ACESSO ' as column: cod1_1_0_ 12:21:42,579 DEBUG StringType:122 - returning 'DESCRICAO APLICACAO ACESSO ' as column: descricao1_0_ 12:21:42,586 DEBUG StringType:122 - returning ' ' as column: versao1_0_ 12:21:42,592 DEBUG TimestampType:122 - returning '2008-01-01 00:00:00' as column: dt5_1_0_ 12:21:42,598 DEBUG StringType:122 - returning 'S' as column: disponivel1_0_ 12:21:42,602 DEBUG StringType:122 - returning '' as column: url1_0_ 12:21:42,608 DEBUG StringType:122 - returning '' as column: mensagem1_0_ 12:21:42,613 DEBUG StringType:122 - returning 'ACESSO ' as column: cod1_1_ 12:21:42,618 DEBUG Loader:972 - found row of collection: [entidades.bdufop.Sistema.aplicacoes#ACESSO ] 12:21:42,640 DEBUG CollectionLoadContext:100 - new collection: instantiating 12:21:42,659 DEBUG StringType:122 - returning 'ACESSO ' as column: cod1_1_ 12:21:42,665 DEBUG StringType:122 - returning 'AP.ACESSO ' as column: codigo1_ 12:21:42,671 DEBUG DefaultLoadEventListener:153 - loading entity: [entidades.bdufop.Aplicacao#component[codigo_sistema,codigo_aplicacao]{codigo_aplicacao=AP.ACESSO , codigo_sistema=ACESSO }] 12:21:42,677 DEBUG DefaultLoadEventListener:304 - attempting to resolve: [entidades.bdufop.Aplicacao#component[codigo_sistema,codigo_aplicacao]{codigo_aplicacao=AP.ACESSO , codigo_sistema=ACESSO }] 12:21:42,687 DEBUG DefaultLoadEventListener:313 - resolved object in session cache: [entidades.bdufop.Aplicacao#component[codigo_sistema,codigo_aplicacao]{codigo_aplicacao=AP.ACESSO , codigo_sistema=ACESSO }] 12:21:42,712 DEBUG Loader:709 - done processing result set (1 rows) 12:21:42,716 DEBUG AbstractBatcher:334 - about to close ResultSet (open ResultSets: 1, globally: 1) 12:21:42,721 DEBUG AbstractBatcher:319 - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) 12:21:42,757 DEBUG AbstractBatcher:470 - closing statement 12:21:42,806 DEBUG ConnectionManager:398 - aggressively releasing JDBC connection 12:21:42,815 DEBUG ConnectionManager:435 - releasing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)] 12:21:42,821 DEBUG Loader:839 - total objects hydrated: 1 12:21:42,829 DEBUG TwoPhaseLoad:107 - resolving associations for [entidades.bdufop.Aplicacao#component[codigo_sistema,codigo_aplicacao]{codigo_aplicacao=AP.ACESSO , codigo_sistema=ACESSO }] 12:21:42,834 DEBUG DefaultLoadEventListener:153 - loading entity: [entidades.bdufop.Sistema#ACESSO ] 12:21:42,874 DEBUG DefaultLoadEventListener:230 - creating new proxy for entity 12:21:43,422 DEBUG TwoPhaseLoad:206 - done materializing entity [entidades.bdufop.Aplicacao#component[codigo_sistema,codigo_aplicacao]{codigo_aplicacao=AP.ACESSO , codigo_sistema=ACESSO }] 12:21:43,427 DEBUG CollectionLoadContext:262 - 2 collections were found in result set for role: entidades.bdufop.Sistema.aplicacoes 12:21:43,432 DEBUG CollectionLoadContext:206 - collection fully initialized: [entidades.bdufop.Sistema.aplicacoes#ACESSO] 12:21:43,436 DEBUG CollectionLoadContext:206 - collection fully initialized: [entidades.bdufop.Sistema.aplicacoes#ACESSO ] 12:21:43,441 DEBUG CollectionLoadContext:272 - 2 collections initialized for role: entidades.bdufop.Sistema.aplicacoes 12:21:43,445 DEBUG StatefulPersistenceContext:748 - initializing non-lazy collections 12:21:43,449 DEBUG Loader:1935 - done loading collection 12:21:43,453 DEBUG DefaultInitializeCollectionEventListener:61 - collection initialized -- 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

17 years, 3 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2010) getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected.

by Lari Hotari (JIRA)

getForUpdateString is not correct in DB2Dialect; session.lock doesn't work as expected. --------------------------------------------------------------------------------------- Key: HHH-2010 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2010 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3, 3.2.0.cr3 Environment: 3.1.3, DB2 Reporter: Lari Hotari The correct getForUpdateString for DB2 should be "for update with rr" see: http://opensource.atlassian.com/projects/hibernate/browse/HB-1032 DB2 will release all locks created in a result set if the isolation level is lower than TRANSACTION_SERIALIZABLE (RR in DB2). Locks and concurrency control in DB2: http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.do... " The duration of row locking varies with the isolation level being used: * UR scans: No row locks are held unless row data is changing. * CS scans: Row locks are only held while the cursor is positioned on the row. * RS scans: Only qualifying row locks are held for the duration of the transaction. * RR scans: All row locks are held for the duration of the 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

17 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2116) CLONE -explicit and implicit query with enabled filter gives different results

by Armin Haaf (JIRA)

CLONE -explicit and implicit query with enabled filter gives different results ------------------------------------------------------------------------------ Key: HHH-2116 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2116 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: hibernate 3.2.0.cr2, hibernate annotations 3.2.0.cr1 Reporter: Armin Haaf we are playing around with filters and found a inconsistent behaviour in using a filter in an explicit vs. implicit join. In explicit join a filter is not active, but in an implicit join it is active. Please look at the attachment -- 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

17 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2104) Infinite recursion in org.hibernate.cfg.Configuration.setListener(String, Object)

by Daniel Beer (JIRA)

Infinite recursion in org.hibernate.cfg.Configuration.setListener(String, Object) --------------------------------------------------------------------------------- Key: HHH-2104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2104 Project: Hibernate3 Type: Bug Components: core Versions: 3.1 rc 1 Environment: Hibernate 3.1, but also newer versions contain this bug. Reporter: Daniel Beer When method org.hibernate.cfg.Configuration.setListener(String, Object) is called with second argument set to <null> (in order to remove all listeners of that type) an infinite recursion occurs. Cause: There is a check against null in this method which invokes a wrong method (its a simple typos): if ( listener == null ) { setListener( type, null ); } Instead the method "setListeners(String, Object[])" should be invoked (notice the trailing "s" in the methods name). -- 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

17 years, 3 months

2
1
0 / 0

[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

17 years, 3 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

17 years, 3 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

17 years, 3 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2007