feat: schema migration

[TimoKramer]

SUMMARY

• schema migration as norm namespace in datahike.
• github discussion: Schema migrations #582
• fixes Schema Migration #13
• relates to [Bug]: schema updates and removals are not consistent #532

Checks

Feature

• Implements an existing feature request. Make sure the feature request has been accepted for implementation before opening a PR.
• Related issues linked using fixes #number
• Documentation added
• Formatting checked

[TimoKramer]

@fpischedda I am thinking since you wished for a way to avoid conflicting schema migrations with colleagues that we could have something like a tool that tracks the migrations in a separate file. Then you would get merge conflicts in case you didn't rebase the last commit to this tracking file. @kordano came up with the idea, there is a tool called atlas for sql-dbs that does this already.

[fpischedda]

Hi @TimoKramer

This is a neat idea! I will also have a look at atlas, it could be useful at $work, thanks @kordano for mentioning it 🙂

[jsmassa]

I think there is something missing in the documentation that describes in which cases it makes sense to use norms for schema migration. For someone that hasn't read the conversation in this issue it doesn't become quite clear why you would need to have norms installed for something that would need to be done only once, naively assuming you only have one database of a kind.

[whilo]

Overall looks good, but I will still need to take a closer look after the clarifications.

[jsmassa]

I like it much better now. I think the "Why using the schema migration tool?" section prevents the confusion I felt in the first version for a new reader.

The resources/.touch file slipped in again though and can be removed.

[kordano]

There is still an empty resources/.touchin there.

[kordano]

Very nice tests. Can you think of any edge cases where the norms might break?

[TimoKramer]

Thanks, I am not aware of any right now.

I leave it to the other reviewers to have the final word on this.