-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert install_model to declarative mapping #12756
Merged
mvdbeek
merged 23 commits into
galaxyproject:dev
from
jdavcs:dev_install_model_declarative
Oct 21, 2021
Merged
Convert install_model to declarative mapping #12756
mvdbeek
merged 23 commits into
galaxyproject:dev
from
jdavcs:dev_install_model_declarative
Oct 21, 2021
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
This class is not referenced in the codebase. The table has limited use, but not through the model, so, I think, it shouldn't be part of the model. The table is part of our SQLAlchemy Migrate setup, which is being replaced with Alembic.
Also, setup Base class for declarative
jdavcs
added
status/WIP
kind/refactoring
cleanup or refactoring of existing code, no functional changes
area/testing
area/database
Galaxy's database or data access layer
labels
Oct 20, 2021
Rename metadata to metadata_. This will break things. (we are only renaming the model attribute, not the table column) Next step: rename all instances of [ToolShedRepository].metadata in code base.
jdavcs
force-pushed
the
dev_install_model_declarative
branch
from
October 21, 2021 00:59
a44d779
to
404bac3
Compare
jdavcs
changed the title
[WIP] Convert install_model to declarative mapping
Convert install_model to declarative mapping
Oct 21, 2021
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/database
Galaxy's database or data access layer
area/testing
kind/refactoring
cleanup or refactoring of existing code, no functional changes
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.
Progress toward #10369 and #12541 (and the no-longer-elusive declarative bliss)
(Same justification as in #12666)
To do:
Technical dept:
I'll handle test setup duplication in the following PR (it's out of scope, better fit for a separate set of commits)
How to test the changes?
(Select all options that apply)
License