Der fellow hibernated,
I'm persisting a List of strings as a <List> with <Element type="string"
not-null="false" column="..">.
With Version 3.3.3 and 3.4.1 i observiert some stange behavieur.
Null values are silently droped on their way to the database. I.e. having 4
elements with 3rd=null you will See elements 1, 2 and 4 in the database and
only a gap for the 3rd. Reading the list, the null will bei filled in for the
third. (I can live with that).
But if you only have 3 elements you will get 2, if the last was null.
I constructed a NH user type instead of string as work around, but is
NullSaveSet will not even be called for the null value. So I have no idea how
to get around this ....
Is this expected behave?
Can't check NH Versions >=4.x.x since this is a 300000 line code base using
iesi sets heavily.
Any ideas for a work around? Or alternativ mapping? I need each string on his
original position.
Thanks
Andreas
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
