Repository navigation
fix(postgresql): drop global Dapper underscore name mapping - #42
Merged
Merged
Conversation
Alias the snake_case columns in the PostgreSQL SELECT instead of enabling Dapper.DefaultTypeMap.MatchNamesWithUnderscores process-wide. Closes #23 BREAKING CHANGE: the PostgreSQL provider no longer sets Dapper.DefaultTypeMap.MatchNamesWithUnderscores = true. Applications that relied on it for their own Dapper queries must set it explicitly at startup.
…dapper-typemap # Conflicts: # AGENTS.md # tests/AspNetCore.DataProtection.CustomStorage.Tests/PostgreSQL/PostgreSqlDataProtectionRepositoryTests.cs
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.
Alias the snake_case columns in the PostgreSQL
SELECT(id AS "Id", ... vianameof(DataProtectionKeyEntity.X)) instead of enablingDapper.DefaultTypeMap.MatchNamesWithUnderscoresprocess-wide at registration time.PersistKeysWithDapperInPostgreSQLand from the PostgreSQL test fixture.Id,InsertDate,FriendlyName,Xmlwith the setting explicitlyfalse, and a unit test asserting the extension leaves itfalse.Closes #23
BREAKING CHANGE: the PostgreSQL provider no longer sets
Dapper.DefaultTypeMap.MatchNamesWithUnderscores = true. Applications that relied on it for their own Dapper queries must set it explicitly at startup.