We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
conda_package_build
Follows up #961
Currently, the conda_package_build table has a column for the channel the package comes from (ref: https://github.com/conda-incubator/conda-store/blob/main/conda-store-server/conda_store_server/_internal/orm.py#L786). However, this is redundant information because each entry must also have a conda_package entry associated to it, which already has the channel information (https://github.com/conda-incubator/conda-store/blob/main/conda-store-server/conda_store_server/_internal/orm.py#L743).
conda_package
This duplication of information can lead to inconsistencies, for example the bug resolved by #961.
This change will simplify the database relations.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Context
Follows up #961
Currently, the
conda_package_build
table has a column for the channel the package comes from (ref: https://github.com/conda-incubator/conda-store/blob/main/conda-store-server/conda_store_server/_internal/orm.py#L786). However, this is redundant information because each entry must also have aconda_package
entry associated to it, which already has the channel information (https://github.com/conda-incubator/conda-store/blob/main/conda-store-server/conda_store_server/_internal/orm.py#L743).This duplication of information can lead to inconsistencies, for example the bug resolved by #961.
Value and/or benefit
This change will simplify the database relations.
Anything else?
No response
The text was updated successfully, but these errors were encountered: