Resolve models by configured table name - #111
Closed
nertzy wants to merge 1 commit into
Closed
Conversation
nertzy
force-pushed
the
resolve-configured-table-name
branch
from
September 4, 2026 22:57
663bbdc to
6d5a676
Compare
nertzy
force-pushed
the
resolve-configured-table-name
branch
from
September 4, 2026 23:15
6d5a676 to
0a0819e
Compare
Collaborator
Author
|
Superseded by #113 in the maintainer-owned stack. |
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.
FixtureBuilder currently infers a model class from each table name. This misses loaded models that configure
self.table_nameand can select a conventionally named model that actually points to a different physical table.Resolve loaded Active Record models by their configured table ownership before writing fixture output. Model-backed extraction now preserves custom attribute serialization, while model-less and id-less tables continue using raw SQL. Ambiguous ownership raises a deterministic error instead of depending on model load order.
Fixes #109