May 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3662) Merging read-only entities causes AssertionError("Merged entity does not have status set to MANAGED...")

by jpk (JIRA)

Merging read-only entities causes AssertionError("Merged entity does not have status set to MANAGED...") -------------------------------------------------------------------------------------------------------- Key: HHH-3662 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3662 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Windows XP Reporter: jpk What worked for me in 3.2.6 now doesn't: merging read-only entities. The following error now occurs when attempting to merge an entity: org.hibernate.AssertionFailure: Merged entity does not have status set to MANAGED; EntityEntry[com.tll.model.impl.AccountHistory#71794688](READ_ONLY) status=READ_ONLY Note this entity class of mine has the @Immutable annotation and removing it prevents this AssertionError from occurring. -- 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

15 years, 8 months

4
14
0 / 0

[Hibernate-JIRA] Commented: (HHH-1872) Hibernate should handle hbm.auto = update with views

by Petr Polak (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1872?page=c... ] Petr Polak commented on HHH-1872: --------------------------------- Maybe another solution would be to allow to "exclude" entity from schema generation. > Hibernate should handle hbm.auto = update with views > ---------------------------------------------------- > > Key: HHH-1872 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1872 > Project: Hibernate Core > Issue Type: Improvement > Components: metamodel > Affects Versions: 3.2.0.cr2 > Reporter: Sami Dalouche > Priority: Minor > > Let's consider a situation where Hibernate domain objects are mapped to a view. > Everything works fine unless hbm.auto = update. In this case, Hibernate tries to update the schema, and of course, it fails. > In this case, hibernate should detect that the object is a view, and only check whether the schema is compatible. It should not try to update the metadata. -- 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

15 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (ANN-369) @CollectionOfElements on a Map uses reserved word "key" as column name

by Martin (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-369?page=co... ] Martin closed ANN-369. ---------------------- > @CollectionOfElements on a Map uses reserved word "key" as column name > ---------------------------------------------------------------------- > > Key: ANN-369 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-369 > Project: Hibernate Annotations > Issue Type: Bug > Components: binder > Affects Versions: 3.2.0.cr1 > Environment: Hibernate 3.2.0cr1, MySQL 5 > Reporter: Martin > Assignee: Emmanuel Bernard > Fix For: 3.2.0.cr2 > > Attachments: dont_use_key_for_maps.diff > > > This annotation > [User.java] > @CollectionOfElements > public Map<String, String> getMisc() > results in this create table statement: > create table User_misc (User_id bigint not null, element varchar(255), key varchar(255), primary key (User_id, key)) type=InnoDB > But "KEY" is a reserved word, so MySQL won't create that table. The default column name should either change or be enclosed by backticks. -- 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

15 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-828) Use Bean Validation for DDL generation

by Emmanuel Bernard (JIRA)

Use Bean Validation for DDL generation -------------------------------------- Key: ANN-828 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-828 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Emmanuel Bernard Fix For: 3.5 -- 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

15 years, 8 months

1
1
0 / 0

[Hibernate-JIRA] Created: (ANN-827) Integrate Bean Validation into Hibernate Annotations

by Emmanuel Bernard (JIRA)

Integrate Bean Validation into Hibernate Annotations ---------------------------------------------------- Key: ANN-827 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-827 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Emmanuel Bernard Fix For: 3.5 -- 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

15 years, 8 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2766) many-to-one with property-ref run into an recursive issue

by René Fuchs (JIRA)

many-to-one with property-ref run into an recursive issue --------------------------------------------------------- Key: HHH-2766 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2766 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Informix 10 Reporter: René Fuchs With many-to-one and property-ref, hibernate resolve always the whole referenced entity. So we have alway an eager issue. If the resolved entity includes one or more other references to non primary keys, these entities will be also resolved and so on. In a big legacy database, if I read only one entity, I get 100 selects or a very very long joined sql (fetch="join"). I think the problem ist located in: org.hibernate.type.EntityType public Object resolve(Object obj, SessionImplementor sessionimplementor, Object obj1) -- 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

15 years, 8 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3877) "Left join Fetch" "With Clause" Required

by Sandeep Vaid (JIRA)

"Left join Fetch" "With Clause" Required ---------------------------------------- Key: HHH-3877 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3877 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.3.1 Reporter: Sandeep Vaid Priority: Blocker Product and ProductBasic has one-to-one relationship Product ---> ProductID <<PK>> ProductBasic ----> ProductId, useCode, StartTime as composite key..... this startTime's value will be known as runtime. Now i want to define mapping between Product & ProductBasic, how will i do it ? Moreover suppose i define their mapping as product.productID = productBasic.productID and useCode='a' as : Product.hbm.xml: <one-to-one name="productBasic" class="ProductBasic" cascade="save-update" property-ref="activeProduct" lazy="proxy" constrained="true"> <formula>'008'</formula> <formula>PRODUCTID</formula> </one-to-one> ProductBasic.hbm.xml as : <properties name="activeProduct"> <property name="useCode" column="USECODE"></property> <many-to-one name="productBO" class="ProductBO" column="PRODUCTID" insert="false" update="false"/> </properties> How can i specify startTime value at runtime (say in eager fetching)? I can't use "inner join fetch" along "with clause".. ? Or i want to specify a condition in fetch join that startTime<currentTime<endtime. the value of currenttime will be known at runtime...How to make this work? -- 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

15 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3897) <One-to-one> Filter Required

by Sandeep Vaid (JIRA)

<One-to-one> Filter Required ---------------------------- Key: HHH-3897 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3897 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.3.1 Reporter: Sandeep Vaid Priority: Critical Consider this scenatio : I have one-to-one relation between Product and ProductBasic BUT at database level i have one-to-many between PRODUCT and PRODUCTBASIC tables as history is mainted in the same table : PRODUCT ----> PID (PK) PRODUCTBASIC ---> PID (FK), USECODE forms Composite-key PRODUCT PID PNAME 1 Pen PRODUCTBASIC PID USECODE STARTTIME ENDTIME 1 100 06-MAY-2009 11:00 07-MAY-2009 10:00 1 100 07-MAY-2009 10:00 31-DEC-9999 00:00 Now while querying for ProductBasic, i will always fetch the row which satisfies the condition STARTTIME<CURRENTTIME<ENDTIME and this will surely return me only one row. Ideally the generated sql query should be : select * from PRODUCT product left outer join PRODUCTBASIC productbasic on '100'=productbasic.USETYPE and product.PID=productbasic.PID and ( productbasic.STARTTIME<'09-MAY-2009 10:00' and '09-MAY-2009 10:00'<productbasic.ENDTIME ) where product.PID='1' -- 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

15 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3677) g

by pioneer (JIRA)

g - Key: HHH-3677 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3677 Project: Hibernate Core Issue Type: Sub-task Reporter: pioneer -- 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

15 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-799) very bad hibernate performance

by gimenete (JIRA)

very bad hibernate performance ------------------------------ Key: ANN-799 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-799 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: http://terrazadearavaca.blogspot.com/2008/12/jpa-implementations-comparis... Reporter: gimenete Priority: Blocker http://terrazadearavaca.blogspot.com/2008/12/jpa-implementations-comparis... -- 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

15 years, 8 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2009