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
Theoretically, the property name could be UdtTypeName, in which case a configuration mechanism should be provided.
Motivation
My goal is to write a custom DataTable converter for Npgsql, enabling its use in a manner similar to how it functions with SQL Server. DataTable can be represented as an array of composite types, making it quite feasible to transfer the table to the server (at least for primitive types like int, long. string, etc)
However, the driver is designed such that if multiple composite types are mapped to the same converter, the first one will be selected. This will result in the data sent not matching the signature of the stored procedure (OIDs).
One option is to initialize the property before passing the parameter to the driver, so that the filtering is accurate, but transparent to the client. This would help eliminate the need to explicitly create parameters and make the transition between databases smoother.
The text was updated successfully, but these errors were encountered:
Proposal
Is it possible to make changes like these in the method TableValuedParameter.AddParameter:
Theoretically, the property name could be UdtTypeName, in which case a configuration mechanism should be provided.
Motivation
My goal is to write a custom
DataTable
converter forNpgsql
, enabling its use in a manner similar to how it functions withSQL Server
.DataTable
can be represented as an array of composite types, making it quite feasible to transfer the table to the server (at least for primitive types likeint
,long
.string
, etc)However, the driver is designed such that if multiple composite types are mapped to the same converter, the first one will be selected. This will result in the data sent not matching the signature of the stored procedure (OIDs).
One option is to initialize the property before passing the parameter to the driver, so that the filtering is accurate, but transparent to the client. This would help eliminate the need to explicitly create parameters and make the transition between databases smoother.
The text was updated successfully, but these errors were encountered: