-
Notifications
You must be signed in to change notification settings - Fork 18
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
Scripts for local file migrations. Closes #642. #648
Scripts for local file migrations. Closes #642. #648
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can also do an action_rename on:
hasOrderedMember -> hasMember.
It might be worth adding in the detect_removed error message that we will be providing sample triples to illustrate the model changes and how they will need to change their data.
Otherwise looks good to me.
@Jamie-SA Since you wrote this we have also deleted |
I've still got a couple more things to do on this PR, but have to switch gears right now and come back to it later. |
I'm not sure what specifically you were referencing. Try to make suggestions for everything that changed? |
Yeah, never mind that last comment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you add the renaming of the conversion factor predicates I mentioned? I don't see it. Both standardConversionFactor
and baseConversionFactor
are renamed to conversionFactor
.
Once that's done, I think these are good to go unless you want to do anything else.
Sorry, missed the conversion factor renaming. I've pushed another change to include that. |
I think I am done now. Please review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. The only thing I would add to the readme is that the migrations scripts are not cumulative - I.e. someone on v9 must upgrade to v10 first and then v11. (That's what I was trying to get at when I suggested mentioning v10, but this is a more generic way to say it.)
@bolerio We are aiming to get this merged by EOD today. Will you have a chance to review it before then? |
I made a couple more changes to address RY's last comment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Migration scripts from v10.0 to v11.0
Closes #642.
I think I covered what we can in the queries
I wrote a very simple test file in
./input/
to be able to do some testing.