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
At present, my application uses Npgsql as the database provider for the main application. However, without wanting to run a blank database for unit testing, I would hope to use an InMemory provider instead.
When a column datatype (e.g. PhysicalAddress) is supported by one provider (Npgsql -> macaddr) but not another, it breaks testing. If a value conversion is entered (e.g.)
That being said, this made us think that configuring value converters for only one provider or another could be useful, and would be nice to do as part of #10784, which is about global conversions.
At present, my application uses Npgsql as the database provider for the main application. However, without wanting to run a blank database for unit testing, I would hope to use an InMemory provider instead.
When a column datatype (e.g. PhysicalAddress) is supported by one provider (Npgsql -> macaddr) but not another, it breaks testing. If a value conversion is entered (e.g.)
This works when using the InMemory provider, but not in the actual implementation.
Ideally, the conversion should be optional, used if the provider does not have native support for that type.
The text was updated successfully, but these errors were encountered: