issue_comments: 281344829
This data as json
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/ACEmulator/ACE/issues/20#issuecomment-281344829 | https://api.github.com/repos/ACEmulator/ACE/issues/20 | 281344829 | MDEyOklzc3VlQ29tbWVudDI4MTM0NDgyOQ== | 570040 | 2017-02-21T13:31:44Z | 2017-02-21T13:31:44Z | CONTRIBUTOR | For a solution that doesn't require migration authors to worry about that, do something similar to the pull request I created where it tracks the database migrations that have run and only runs them once, in sequential order. That is relatively standard for database-backed applications. You will also run into difficulty with migrations where they are interdependent, i.e. one migration needs to run before another one can be run, because it creates or alters tables used by the other migration. My pull request took all this into account. With your PowerShell solution you could probably track the migrations that have run in a text file or registry key. > On Feb 21, 2017, at 7:36 AM, Mogwai-AC <notifications@github.com> wrote: > > The scripts would need to be altered to be re-run safe. MySQL's support for this is spotty, but it could be done. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread. > | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 205353528 |