fix: complete SQLAlchemy inheritance pattern support (STI, JTI, CTI) #611
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
This PR completes the implementation of SQLAlchemy inheritance pattern support in
CommonTableAttributes, enabling proper handling of Single Table Inheritance (STI), Joined Table Inheritance (JTI), and Concrete Table Inheritance (CTI).Changes
Core Implementation (advanced_alchemy/base.py)
Added
__init_subclass__hook (lines 209-277):polymorphic_onin their__mapper_args__cls.__tablename__ = Nonefor STI childrenpolymorphic_identity) and implicit (without) STI childrenEnhanced
@declared_attr.__tablename__()method (lines 281-386):Nonefor explicitly setNonevalues (set by__init_subclass__)Supported Patterns
✅ Single Table Inheritance (STI):
polymorphic_identityshare parent's tablepolymorphic_identity(with warning)✅ Joined Table Inheritance (JTI):
__tablename__create joined tables✅ Concrete Table Inheritance (CTI):
concrete=Truecreate independent tablesRelated Issues
Supersedes PR #600