Resolve models by configured table name - #113
Open
nertzy wants to merge 1 commit into
Open
Conversation
This was referenced Sep 5, 2026
nertzy
force-pushed
the
resolve-configured-table-name-rdy
branch
from
September 5, 2026 01:30
3282a12 to
4f487c8
Compare
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
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
table_nameand connection poolWhy
Fixture generation currently infers model constants from conventional table names. Rails applications can move a model to a different table with
self.table_name, and those tables silently fall back to raw SQL. The fallback bypasses model-backed serialization and can emit database-native values instead of the fixture values Rails expects.