February 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (METAGEN-9) Implement mixed configuration (annotation + xml)

by Hardy Ferentschik (JIRA)

Implement mixed configuration (annotation + xml) ------------------------------------------------ Key: METAGEN-9 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-9 Project: Hibernate StaticMetamodel Generator Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik At the moment only xml or annotations are considered. Configurations have to be "merged" -- 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, 11 months

1
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1414) many-to-many and metadata order-by based on column from the target table

by Aayush (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1414?page=c... ] Aayush commented on HHH-1414: ----------------------------- great. thanks for fixing it. I came across this situation and it took me a while to finally land on this page to figure out wht to do. for other who come to this page. here is what my many-to-many mappings look like <set name="senders" table="Email_Folder_X_Sender"> <key column="folder_Id"/> <many-to-many column="sender_id" class="com.Sender" order-by="sender_description"/> </set> > many-to-many and metadata order-by based on column from the target table > ------------------------------------------------------------------------ > > Key: HHH-1414 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1414 > Project: Hibernate Core > Issue Type: Improvement > Components: metamodel > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.0.cr2 > > > Much like we do for filter and where, allow order-by on the <many-to-many/> itself -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4902) Handle JPA 2 requirement of setting id attribute to non-null with its equivalent of foreign-generator

by Steve Ebersole (JIRA)

Handle JPA 2 requirement of setting id attribute to non-null with its equivalent of foreign-generator ----------------------------------------------------------------------------------------------------- Key: HHH-4902 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4902 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Next JPA 2 defines an equivalent of the Hibernate foreign generator. However the spec implies (via a badly worded footnote) that users can manually set a value for that id attribute. However the spec is very clear that it is the association which drives the persisted id value, not the id attribute. So basically, the user can manually set the id value but it is completely expected to be ignored. Unfortunately that messes up the Hibernate notion of unsaved-value (how it distinguishes transient entities from detached entities). So we need to account for this in the persist listeners. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4901) One should not map IdClass properties in the mapping

by Emmanuel Bernard (JIRA)

One should not map IdClass properties in the mapping ---------------------------------------------------- Key: HHH-4901 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4901 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.0-Beta-4 Reporter: Emmanuel Bernard A better fix for HH-4895 is explained below AbstractEntityPersister#1847 we try and map the identifier with "id" (as no property named "id" is present) The path is then nullified when calling initComponentPropertyPaths (it's not a qualified path) We end up "remapping" the emp property but the one from the IdClass which is returned by getIdentifierType() in AbstractEntityPersister HbmBinder does map it twice but since we don't have the type mismatch between idclass and the actual property hosted by the entity we don't fall into this bug Somehow, we should not run AbstractEntityPersister#1847 if getIdentiierType() is the IdClass (ie there is an identifier mapper but I don't know how to detect that) -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4731) Public API to know if an entity class is audited

by Hernán Chanfreau (JIRA)

Public API to know if an entity class is audited ------------------------------------------------ Key: HHH-4731 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4731 Project: Hibernate Core Issue Type: New Feature Components: envers Affects Versions: 3.5.0-Beta-2 Environment: envers build from trunk (2009-12-22) Reporter: Hernán Chanfreau Priority: Trivial Attachments: isEntityClassAuditedPatch.txt Expose audit meta data information for an entity class vía AuditReader API. Here is a little discussion: http://community.jboss.org/message/517432#517432 Here is a patch for supporting this feature. I created a simple test too. Thanks. Hernán. -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4900) Wrong immutable type check in IdMetadataGenerator

by Slawek Garwol (JIRA)

Wrong immutable type check in IdMetadataGenerator ------------------------------------------------- Key: HHH-4900 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4900 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-4 Reporter: Slawek Garwol Attachments: fixForImmutableTypeCheck.zip Check is performed by checking if type is instance of ImmutableType. Should invoke propertyType.isMutable() Fix and test case is attached -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-772) null in maps are handled inconsistently

by Stefan Fromm (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-772?page=co... ] Stefan Fromm commented on HHH-772: ---------------------------------- I also stumbled on this issue. I expected the map to persist null values. Could not there be a setting in the mappings definition, with which one could enable the saving of keys with null values for map properties? Thus old behaviour could be preserved. > null in maps are handled inconsistently > --------------------------------------- > > Key: HHH-772 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-772 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Max Rydahl Andersen > Fix For: 3.1 beta 1 > > > regarding case 00004729. > group.getUsers().put("something", null); > Does not result in any insert. > Inserting "something", null manually into the underlying table and > when hibernate reads the map will have "something"->null in the map. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4896) Read-only proxy targets initialized from second-level cache are not read-only

by Gail Badner (JIRA)

Read-only proxy targets initialized from second-level cache are not read-only ----------------------------------------------------------------------------- Key: HHH-4896 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4896 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.0-Next Read-only proxy targets initialized from second-level cache are not read-only. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4898) Results from read-only Criteria and Query obtained from query cache are not read-only

by Gail Badner (JIRA)

Results from read-only Criteria and Query obtained from query cache are not read-only ------------------------------------------------------------------------------------- Key: HHH-4898 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4898 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.0-Next Results from read-only Criteria and Query obtained from query cache are not read-only. -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4578) Criteria is missing read-only flag

by Ales Justin (JIRA)

Criteria is missing read-only flag ---------------------------------- Key: HHH-4578 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4578 Project: Hibernate Core Issue Type: Improvement Components: query-criteria Affects Versions: 3.5.0-Beta-2 Reporter: Ales Justin Attachments: readOnly.patch Query API has a notion of read-only, whereas Criteria doesn't. * https://forum.hibernate.org/viewtopic.php?p=2353610&sid=98ea30c01ac78df6a... Is this intentional or oversight? -- 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, 11 months

4
9
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 2010