database: Add categories
and keywords
columns to the versions
table
#10078
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.
Similar to #9998, this PR adds two new columns to the
versions
database table:categories
andkeywords
These columns are filled with the corresponding values from the
Cargo.toml
file when new crates/versions are published.Compared to the per-crate categories and keywords, these are not saved in dedicated
crates_categories
andcrates_keywords
tables, but just as a regular Postgres array column. The reason for this is that we don't need to find versions by category or keyword. We only need the data to set the new crate categories/keywords when the "default version" of a crate changes (will be implemented in a follow-up PR, once the data is backfilled in the database).Related: