Adapt importer to the latest schema/ORM changes #51
Conversation
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
2 participants
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.
Following the schema change (metabrainz/bookbrainz-site#1136) and the ORM change (metabrainz/bookbrainz-data-js#323), the importer tools and the test data also have to be adapted (mostly because of improved terminology to be honest).
Additionally I realized that it is possible to create edition imports which are not linked to an edition group, so it makes a lot of sense to remove the unstable EG BBID from the test data.
The whole thing is possible because there are still editions without edition group from an older schema in the DB, so the column is still nullable.