Closed dallmair closed 3 years ago
How about just adding a constructor overload that takes a name? Seems simpler than deriving. https://github.com/terrajobst/nquery-vnext/blob/master/src/NQuery.Data/DataTableDefinition.cs
Oh wow, was so deep down in the current workaround implementation that I didn't see the obvious solution. Thanks for pointing me towards the right direction!
So, PR #35 adds the proposed constructor overload.
Completed by #35
We'd like to use NQuery with
System.Data.DataTable
instances, but provide individual names instead of relying onDataTable.TableName
. For this, it would be great ifDataTableDefinition
would not be sealed, because then we could simply override theName
property.Would this be ok for you, or shall we implement an own derivative of
TableDefinition
?