[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1690) collection (set) always treated as dirty if it consists of composite-elements

[Michael Prescott (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1690?page=comments#action_24793 ] 

Michael Prescott commented on HHH-1690:
---------------------------------------

I ask because I have a scenario where the default (Object) semantics are acceptable to me, and we're never comparing these elements across sessions.  Nevertheless, a one-element set is always marked as dirty.

> collection (set) always treated as dirty if it consists of composite-elements
> -----------------------------------------------------------------------------
>
>          Key: HHH-1690
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1690
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3
>  Environment: jdk1.5
>     Reporter: Renat Araslanow

>
>
> collection (set) always treated as dirty if it consists of composite-elements (lazy and access type doesn't matter).
> if i change composite-element to element with type string all is all right.
> User.hbm.xml
> 		<set name="z" access="field" table="user_roles"  lazy="false">
> 			<key column="account_id"/>
> 			<composite-element class="indoors.model.UserRole">
> 				<property name="role" not-null="true" type="string"/>
> 			</composite-element>
> 		</set>
> User.java (only that relate to collection this single line)
> ...
> 	private Set z = new HashSet();
> ...
> UserRole.java
> public class UserRole 
> {
> 	private String role;
> 	public String getRole()
> 	{
> 		return role;
> 	}
> 	public void setRole( String role )
> 	{
> 		this.role = role;
> 	}
> }

-- 
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.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira