There is a ICompositeUserType, where you can define several columns. You could also make it parameterized, to define in the mapping which columns exist. It depends on what problem you have actually to solve.
On 18 Mai, 09:42, martin <[email protected]> wrote: > I like the way <dynamic-component> enables me to map a configurable > amount of columns to my database table. > > But I dislike that it forces me to use a IDictionary at my POCO. Will > it be possible to implement my own <dynamic-component> type as it is > possible with the IUserType for normal properties? > > (At least having a generic IDictionary<TKey,TValue> implementation > would help a lot.) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
