Wiki Link: [discussion:1957]
Using Materializer with dynamic field set 

Jun 29 2009 at 3:33 PM
Was hoping to get some guidance for using materializers with dynamic fields returned.

Calling a proc that returns search results, but depending on the search options, certain columns may/may not be returned in the results set.
Is there a preferred method to populate an entity using a func<t1,t2> without having to create a different materializer for each 'shaped' result set?

the only 'neat' way that I've found to do this is too pass a idatareader into the constructor of the entity, however I still haven't found a way to detect if a field actually exists in the result set.

Aug 18 2009 at 7:39 AM
I have the same requirement as parheric as descirbed above. I want to use same materializer for all the result sets returned for particular entity.
Some result sets may contain certain columns and other result sets may not contain it. But want to use same materializer for all the result sets instead of
creating new materializer per result set.

Please provide your feedback on above this.

Mar 10 2010 at 4:16 PM
Is there anyone that can answer this. I have the same requirement as those mentioned in this post and really need to come to a resolusion soon on this.


Page view tracker