Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-613
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-613
Summary: Problem with null composite-elements
Type: Bug
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate2
Components:
core
Versions:
2.1 final
Assignee:
Reporter: William Drai
Created: Fri, 9 Jan 2004 9:52 AM
Updated: Fri, 9 Jan 2004 9:52 AM
Environment: Hibernate 2.1, MySQL 4.1.1
Description:
I have a mapping like this :
<class name="Foo">
<id ../>
<map name="elements" table="ELEMENTS">
<key column="FOO_ID" />
<index column="ELEMENT_ID" />
<composite-element class="Element">
<property name="prop1" />
<property name="prop2" />
</composite-element>
</map>
</class>
If I store an instance of Foo with one element in the map where prop1 and prop2 are null, all is ok in the database :
ELEMENT_ID | PROP1 | PROP2
"element" | null | null
When I load this instance of Foo later, I get the "elements" map, but the entry has a key "element" and a null value, instead having a new empty Element instance.
William
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
