By adding a not-nullable option to the component mapping?

On Sat, Jun 27, 2009 at 3:03 PM, Tuna Toksoz <[email protected]> wrote:

> How could we know if it was a real null or its properties are null, when we
> take it from db?
> If we do what you say, than some other person can come and ask the reverse.
>
> Tuna Toksöz
> Eternal sunshine of the open source mind.
>
> http://devlicio.us/blogs/tuna_toksoz
> http://tunatoksoz.com
> http://twitter.com/tehlike
>
>
>
>
>
> On Sat, Jun 27, 2009 at 3:59 PM, Paco Wensveen <[email protected]> wrote:
>
>> I have a mapping with a component. When all properties in the component
>> are null, the whole component is null.
>> I want to return a component with all properties set to null in this case.
>> I know I can work around this by initializing the component field in the
>> getter of the entity class, but that is not perisitent ignorant. Is it
>> possible to do this in the mapping?
>>
>> Thanks!
>>
>> Paco
>>
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to