Add support for upcoming icat.server 6.2 #169
Merged
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
adapting the content, though
DataPublication.internalId, and FundingReference.acknowledgement to example data being used in the tests
RKrahl
added
the
compatibility
example script to the maximum length of entity type name
icat.dump_queries.getDataPublicationQueries()
example script dynamically the maximum length of entity type name
content from icatdump-6.2.yaml instead of icatdump-5.0.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Add support for ICAT schema changes expected in upcoming icat.server 6.2.0:
Subjectinto dump file created byicatdump,icatdump-6.2.*files.Draft, still to do:
icatdump-6.2.*files, update the references to the ICAT version from6.2a0to6.2inconftest.pyandtest_06_query.py,Close #168.