🐛 Fix Field alias support for Pydantic v2 with backward compatibility #1575
+249
−37
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.
Description
This PR fixes the Field(alias="...") functionality that was broken in Pydantic v2 while maintaining full backward compatibility with Pydantic v1.
Problem
In Pydantic v2, the
alias
parameter in SQLModel'sField
function was not working correctly for validation and serialization. The issue was that Pydantic v2 requires explicitvalidation_alias
andserialization_alias
parameters, but SQLModel wasn't automatically propagating thealias
value to these parameters.Solution
Changes Made:
Enhanced Field function:
validation_alias
andserialization_alias
parametersAutomatic alias propagation:
post_init_field_info
in_compat.py
to automatically setvalidation_alias
andserialization_alias
fromalias
when not explicitly provided (Pydantic v2 only)Backward compatibility:
Comprehensive testing:
Breaking Changes
None. This is purely a bug fix with backward compatibility maintained.
Closes
Fixes #1536