February 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-552) Transparent event integration for Search and Validator

by Emmanuel Bernard (JIRA)

Transparent event integration for Search and Validator ------------------------------------------------------ Key: ANN-552 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-552 Project: Hibernate Annotations Type: New Feature Reporter: Emmanuel Bernard Fix For: 3.3.0 breaks current configurations, so tag it for 3.3 -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-528) avoid auto import of superclasses to avoid inheritance mapping

by Armin Haaf (JIRA)

avoid auto import of superclasses to avoid inheritance mapping -------------------------------------------------------------- Key: ANN-528 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-528 Project: Hibernate Annotations Type: New Feature Components: binder Reporter: Armin Haaf It is not possible to avoid inheritance mapping if the superclass of a entity is also a entity. Background: A framework provides a basic mapping of a entity, but I want to extend that. With annotations it is not possible to just map my extended version and have the superclass behave like a MappedSuperclass. This behaviour is acceptable but it is not possible to override a the id generation. So it might be better to have a new annotation (e.g. @RootEntity(mapSuperclass=true)) to avoid auto import of the entity superclass. With that approach it would be easier to create modules and frameworks -- 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, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-557) The BigDecimal is not correct to save to database

by Anton P. (JIRA)

The BigDecimal is not correct to save to database ------------------------------------------------- Key: ANN-557 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-557 Project: Hibernate Annotations Type: Bug Versions: 3.1beta3 Environment: Hibernate-Version: 3.1.3, Oracle 10.0.1 JDK 1.5.0_07-b03 Reporter: Anton P. The release of BigDecimal differents in jvm 1.4 and 1.5. in jvm 1.5 BigDecimal.toString() will return ~ 0E-07 if this 0.0000000 and when hibernate make save this. in that field of table will put 7. that is not good. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6298816 http://www.obscured.info/java/java-5-and-the-bigdecimal/ -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2376) Query with fully qualified entity class fails

by Neukomm (JIRA)

Query with fully qualified entity class fails --------------------------------------------- Key: HHH-2376 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2376 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.1 Environment: Hibernate 3.2.1ga, HSQLDB 1.8.0.4 Reporter: Neukomm Attachments: DiscriminatorTest2.java We've recently ran into a problem while migrating from Hibernate 3.1.1 to Hibernate 3.2.1ga: While queries against the class attribute still work, if the class is non-qualified, the query fails if the name is fully qualified. e.g. "from Person p where p.class = Person" works fine while "from Person p where p.class = org.hibernate.test.discriminator.Person" fails. I've attached a test case to illustrated the problem. It should work when it's put into the 'discriminator' package of the hibernate junit test cases. Both testcases work fine for hibernate versions up to and including 3.2.0cr2. In later versions, specifically in 3.2.1ga, the test case that uses the fully qualified class name ('testQueryWithPackage') fails. -- 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, 10 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2398) Have hi/lo strategies use delegation rather than inheritence

by Steve Ebersole (JIRA)

Have hi/lo strategies use delegation rather than inheritence ------------------------------------------------------------ Key: HHH-2398 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2398 Project: Hibernate3 Type: Improvement Reporter: Steve Ebersole Allows: 1) simplier reusability 2) simplier testability -- 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, 10 months

1
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1276) Add outer join support to Criteria API

by Michal Palicka (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1276?page=c... ] Michal Palicka commented on HHH-1276: ------------------------------------- Hello, is there any chance, that the patch will be included in the official Hibernate release? It is not really convenient to manage our own version of Hibernate and apply various user-patches to every new release. Thank you. > Add outer join support to Criteria API > -------------------------------------- > > Key: HHH-1276 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1276 > Project: Hibernate3 > Type: Patch > Components: core > Versions: 3.1 > Reporter: Jeremy Haile > Attachments: patch.txt > > > Here's a patch that allows users to specify a joinType when calling createCriteria and createAlias on the Criteria interface. This allows you to specify outer joins when creating Criteria. If you have any questions or see anything I missed - let me know. I have tested and am currently using the patch with no problems. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-817) using projections is causing SQL query error on oracle (ORA-00904 error)

by Michal Palicka (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-817?page=co... ] Michal Palicka commented on HHH-817: ------------------------------------ Hello! The query generated by Hibernate is definitely an invalid SQL, since column aliases are not allowed in WHERE clauses. SQL evaluates the statements in the following order: (1) the FROM clause (2) the WHERE clause (3) the SELECT clause When the WHERE clause is being evaluated, the aliases from the SELECT clause are not yet known. There are several links that describe the problem: http://www.sqlhacks.com/index.php/Retrieve/Alias-in-where http://archives.postgresql.org/pgsql-general/2002-11/msg01411.php http://dev.mysql.com/doc/refman/5.0/en/problems-with-alias.html I do not have the SQL standard specification at hand, but the third document (at mysql.com) states that the mentioned behaviour is part of the SQL standard (so it is not a bug in Oracle, Postgres or MySQL). Please, change the priority of this issue to "Critical". Thank you. > using projections is causing SQL query error on oracle (ORA-00904 error) > ------------------------------------------------------------------------ > > Key: HHH-817 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-817 > Project: Hibernate3 > Type: Bug > Versions: 3.0.5 > Environment: Oracle 9.2.0.6, Hibernate 3.0.5, Spring Framework 1.2.2 based application working on Jakarta Tomcat 5.0.28 > Reporter: Michal Jastak > Priority: Minor > > > following java code: > protected Entity loadEntityLightweight(Serializable entityId) throws DataAccessException { > Criteria criteria = getSession().createCriteria(Entity.class); > ProjectionList projectionList = Projections.projectionList(); > projectionList.add(Property.forName(BaseEntity.PROP_ID), BaseEntity.PROP_ID); > projectionList.add(Property.forName(BaseEntity.PROP_TYPE), BaseEntity.PROP_TYPE); > criteria.setProjection(projectionList); > criteria.add(Restrictions.eq(BaseEntity.PROP_ID, entityId)); > criteria.setResultTransformer(new AliasToBeanResultTransformer(Entity.class)); > return (Entity) criteria.uniqueResult(); > } > generates following SQL query: > select this_.id as y0_, this_.type as y1_ from entities this_ left outer join facilities this_1_ on this_.id=this_1_.id left outer join users this_2_ on this_.id=this_2_.id left outer join addresses address2_ on this_.address_id=address2_.id left outer join entities entity3_ on this_2_.employer_id=entity3_.id left outer join facilities entity3_1_ on entity3_.id=entity3_1_.id left outer join users entity3_2_ on entity3_.id=entity3_2_.id where y0_=? > y0_ = ? expression in where clause is causing a 904 error on Oracle 9: > ORA-00904: "Y0_": invalid identifier > hibernate dialect: org.hibernate.dialect.Oracle9Dialect > mapping for Entity class: > <?xml version="1.0"?> > <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" > "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> > <hibernate-mapping default-lazy="false" default-cascade="save-update"> > > <class name="Entity" table="entities" mutable="true"> > <id name="id" type="java.lang.Long" unsaved-value="null"> > <generator class="sequence"> > <param name="sequence">entities_id_seq</param> > </generator> > </id> > <many-to-one name="address" class="Address" column="address_id" /> > ... >  > <joined-subclass name="Facility" table="facilities"> > <key column="id" /> > ... > <set name="users" inverse="true" lazy="true"> > <key column="facility_id" /> > <one-to-many class="User" /> > </set> > </joined-subclass> >  > <joined-subclass name="User" table="users" dynamic-insert="true" dynamic-update="true"> > <key column="id" /> > <many-to-one name="employer" class="Entity" column="employer_id" cascade="none" /> > ... > <set name="userAuthorities" inverse="true" cascade="all-delete-orphan"> > <key column="user_id" /> > <one-to-many class="Authority" /> > </set> > </joined-subclass> > </class> > </hibernate-mapping> -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (HSEARCH-24) Potential deadlock when using multiple DirectoryProviders in a highly concurrent index update

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-24?page... ] Emmanuel Bernard moved ANN-522 to HSEARCH-24: --------------------------------------------- Version: (was: 3.2.1) HAN-3.2.1 (Previous Bundled) Fix Version: (was: 3.2.2) FIRST Component: (was: search) directory provider Key: HSEARCH-24 (was: ANN-522) Project: Hibernate Search (was: Hibernate Annotations) > Potential deadlock when using multiple DirectoryProviders in a highly concurrent index update > --------------------------------------------------------------------------------------------- > > Key: HSEARCH-24 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-24 > Project: Hibernate Search > Type: Bug > Components: directory provider > Versions: HAN-3.2.1 (Previous Bundled) > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: FIRST > > -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (HSEARCH-23) Support asynchronous batch worker queue

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-23?page... ] Emmanuel Bernard moved ANN-520 to HSEARCH-23: --------------------------------------------- Fix Version: (was: 3.2.2) FIRST Component: (was: search) engine Key: HSEARCH-23 (was: ANN-520) Project: Hibernate Search (was: Hibernate Annotations) > Support asynchronous batch worker queue > --------------------------------------- > > Key: HSEARCH-23 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-23 > Project: Hibernate Search > Type: New Feature > Components: engine > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: FIRST > > -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Moved: (HSEARCH-22) Enum value Index.UN_TOKENISED is misspelled

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-22?page... ] Emmanuel Bernard moved ANN-512 to HSEARCH-22: --------------------------------------------- Version: (was: 3.2.1) HAN-3.2.1 (Previous Bundled) Fix Version: (was: 3.2.2) FIRST Component: (was: search) mapping Key: HSEARCH-22 (was: ANN-512) Project: Hibernate Search (was: Hibernate Annotations) > Enum value Index.UN_TOKENISED is misspelled > ------------------------------------------- > > Key: HSEARCH-22 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-22 > Project: Hibernate Search > Type: Bug > Components: mapping > Versions: HAN-3.2.1 (Previous Bundled) > Reporter: Caleb Land > Assignee: Emmanuel Bernard > Priority: Trivial > Fix For: FIRST > > > The enum value Index.UN_TOKENISED should be spelled Index.UN_TOKENIZED (with a z instead of an s) -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2007