feat: add PostgreSQL typed parameter support - #11
Merged
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 19782d8655
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a provider-specific PostgreSQL package for Dapper typed parameters using Npgsql. The new provider keeps PostgreSQL metadata explicit at the call site through
NpgsqlDbType, while preserving the existing SQL Server package contract.What changed
TypedParameters.Dapper.PostgreSqlpackage.TypedPostgresParametercore parameter implementation.PostgresParamfactories for scalar values.jsonandjsonbfactories.date,time,timestamp,timestamptz, andinterval.Architecture
SQL Server and PostgreSQL remain provider-specific packages because their database contracts and ADO.NET provider APIs are meaningfully different. The branch intentionally avoids a shared
TypedDbParameterabstraction so SQL Server features such as output parameters and TVPs do not leak into PostgreSQL, and PostgreSQL features such as arrays, JSON, and timestamp semantics stay explicit.Validation
dotnet --infodotnet restore Dapper.TypedParameters.slndotnet build Dapper.TypedParameters.sln --configuration Release --no-restorenet8.0,net10.0net8.0,net10.0net8.0,net10.0net8.0,net10.0dotnet packfor both provider packagesRunPackageValidationfor both provider packagesnet8.0andnet10.0dotnet list package --vulnerable --include-transitivePackages
TypedParameters.Dapper.SqlServerTypedParameters.Dapper.PostgreSqlRelease pipeline
The release workflow now validates, packs, and publishes the two provider packages separately. Each package keeps its own NuGet identity and package validation path, and the workflow produces independent
.nupkgand.snupkgartifacts before publication.Closes #8