use column transformer for EXCLUDED column name on upsert query of PostgreSQL #886
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.
Requery does not currently use the column transformer when generating EXCLUDED column name in Postgres.
Therefore, when specifying a column transformer that makes the column name a snake case, Requery generate a SQL as bellow:
This query does not work well because the column name used in EXCLUDED clause wasn’t converted correctly (it must be a ‘message_title’, but is a ‘messageTitle’).
In my patch, I changed a UpsertOnConflictDoUpdate class to use a column transformer when generating EXCLUDED column names, so it generates a SQL as bellow: