Are you ever going to query individual fields from these 3rd-party objects or can they be considered as just blobs of data you want retrieved with your object?
A very quick-and-dirty approach for data blobs could be serialize these objects to XML and store that xml in the database. I proably wouldn't consider this to be "best practice" though! On Dec 18, 4:10 am, Al Su <[email protected]> wrote: > Hi all, > > As per subject: > - we have 3rd party library that we can't change; > - this library uses arrays for children collections (it can be arrays > of system types(System.Uri) or library's custom types (2-3 levels > deep) - all public); > - NO ConventionalModelMapper - we want explicitly map all that we need > (to much to exclude); > - we don't want anything from these library but data to persist; > - DB from scratch. > > What will be the best practice solution in this case? > > public class MyType : Entity > { > public virtual TheirType theirtype { get; set; } > ........ > > } > > I have no problem to map simple properties from theirtype, but how can > I map (array) collections here? > > Thank you, > Alex. -- 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.
