I would also say Custom user type be the way to go. Tuna Toksöz Eternal sunshine of the open source mind.
http://devlicio.us/blogs/tuna_toksoz http://tunatoksoz.com http://twitter.com/tehlike On Wed, Apr 8, 2009 at 11:48 PM, Jan Limpens <[email protected]> wrote: > Hello, > > I wonder if anybody know if something like this is mappable: > > public class Document { > public Guid Id {get; set;} > public IDictionary<string, string> Properties {get; set;} > } > > Properties would not be a relation to another table, but just a nvarchar > column in the table. Could be in whatever format (xml, json, ini, ...) > There would be other, relational data as well, so heading for a pure > document based db would not work (and to my knowledge there isn't one just > yet in .net land, apart from blog entries...) > > I suppose, I would have to use a custom user type to de/serialize, but any > first hand experience would be a great help in avoiding pitfalls. > -- > Jan > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
