-
Notifications
You must be signed in to change notification settings - Fork 132
Feature: Introduce PostgreSql support to NpgsqlDbType. #390
Copy link
Copy link
Closed
Labels
deployedFeature or bug is deployed at the current releaseFeature or bug is deployed at the current releasefixedThe bug, issue, incident has been fixed.The bug, issue, incident has been fixed.priorityTop priority feature or things to doTop priority feature or things to dorequestA request from the community.A request from the community.todoThings to be done in the futureThings to be done in the future
Metadata
Metadata
Assignees
Labels
deployedFeature or bug is deployed at the current releaseFeature or bug is deployed at the current releasefixedThe bug, issue, incident has been fixed.The bug, issue, incident has been fixed.priorityTop priority feature or things to doTop priority feature or things to dorequestA request from the community.A request from the community.todoThings to be done in the futureThings to be done in the future
Descriptions
A developer must be able to pass the correct PostgreSql DB Type. Let us say the user would like to make sure the the column Customer.ExtraInfo below is passed as a NpgsqlDbType.Json type.
If ever the user set the value of DbType, it is still not colliding.
As per Shay (the author of Npgsql library), this setting must be explicitly set as Npgsql is using the NpgsqlDbType property instead (over DbType).
Extent of the changes
The changes must be happened in RepoDb.PostgreSql and RepoDb.Core only.
Assessment: Minor
Acceptance Criteria
All existing Integration Tests and Unit Tests must be passed for all libraries and extensions.