You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the DataBinder expects all properties to be found in the csv data, but allows there to be extra columns in the CSV data. GetRecords<T> is a helper method though, and you can call DataBinder.Create and pass in a DataBinderOptions instance that allows specifying the binding mode. These modes are not specified per-column though. I think it would be a reasonable enhancement to allow specifying optional columns with System.Runtime.Serialization.OptionalFieldAttribute.
Note: the DataBinder is DbDataReader agnostic, you can use it with any DbDataReader implementation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
@CaiusJard To continue the SO discussion here...
By default, the DataBinder expects all properties to be found in the csv data, but allows there to be extra columns in the CSV data.
GetRecords<T>
is a helper method though, and you can call DataBinder.Create and pass in aDataBinderOptions
instance that allows specifying the binding mode. These modes are not specified per-column though. I think it would be a reasonable enhancement to allow specifying optional columns withSystem.Runtime.Serialization.OptionalFieldAttribute
.Note: the DataBinder is DbDataReader agnostic, you can use it with any DbDataReader implementation.
Beta Was this translation helpful? Give feedback.
All reactions