🐛 Fix SQLAlchemy type handling in Field - #2095
Merged
Merged
Conversation
Supersedes #1345.
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
1 participant
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.
🐛 Fix SQLAlchemy type handling in
FieldSupersedes #1345. That PR correctly identified the runtime/type-annotation mismatch. This implementation preserves its core fix while narrowing
sa_typeto SQLAlchemy type classes and instances, rather than the broader positional Column argument type.AI Disclaimer
Made with the help of AI, using Codex with
gpt-6-astra, manually reviewed.