Config option to exclude models #169
Merged
Conversation
This file contains 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
slawosz
force-pushed
the
allow-to-exclude-models
branch
from
806d77b to
f1aa702
Compare
slawosz
force-pushed
the
allow-to-exclude-models
branch
from
f1aa702 to
cb1c818
Compare
asatwal
reviewed
Nov 7, 2024
asatwal
pushed a commit
that referenced
this pull request
Nov 25, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This pull request introduces a config option to disable one or more models entirely:
In my application, there were 2 models with very similar names:
Namespace::FooandFoo, pointing to tablefoosin 2 different databases. Becausedfe-analyticsdoes not recognize namespaces or different databases, the above option is a viable solution to the problem. The reason for similar models/tables is migration - one application data is moving to another.