Update migrations.md

[ewjoachim]

Relates to the comments at the end of #1070

@medihack if you have an opinion, or think of something else we should say @alexwilson1 too :) It's certainly possible that we haven't found the root cause of your issue yet, so feel free to communicate !

Successful PR Checklist:

• [ ] Tests
  • [x] (not applicable?)
• [x] Documentation
  • [ ] (not applicable?)

PR label(s):

• [ ] https://github.com/procrastinate-org/procrastinate/labels/PR%20type%3A%20breaking%20%F0%9F%92%A5
• [ ] https://github.com/procrastinate-org/procrastinate/labels/PR%20type%3A%20feature%20%E2%AD%90%EF%B8%8F
• [ ] https://github.com/procrastinate-org/procrastinate/labels/PR%20type%3A%20bugfix%20%F0%9F%95%B5%EF%B8%8F
• [ ] https://github.com/procrastinate-org/procrastinate/labels/PR%20type%3A%20miscellaneous%20%F0%9F%91%BE
• [ ] https://github.com/procrastinate-org/procrastinate/labels/PR%20type%3A%20dependencies%20%F0%9F%A4%96
• [x] https://github.com/procrastinate-org/procrastinate/labels/PR%20type%3A%20documentation%20%F0%9F%93%9A

[github-actions[bot]]

Coverage report

This PR does not seem to contain any modification to coverable code.

[alexwilson1]

Applying migrations below worked for me as mentioned in the other thread:

02.00.03_01_add_job_priority.sql
02.05.00_01_add_periodic_job_priority.sql
02.06.00_01_add_cancel_states.sql

Thanks!

[medihack]

Yes, improving the docs there is a good thing. I understand that handling those migrations can be painful for non-Django users. I am not sure if I would have chosen Procrastinate myself when I was not working with Django.