issues: 205353528
This data as json
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
205353528 | MDU6SXNzdWUyMDUzNTM1Mjg= | 20 | Server should have a way to apply DB migrations | 570040 | closed | 0 | 7 | 2017-02-04T15:19:26Z | 2017-12-04T14:30:37Z | 2017-12-04T14:30:36Z | CONTRIBUTOR | The server should have a way to track which DB migrations it has applied, and automatically apply missing ones in the correct order. @Mag-nus suggested a naming convention of `YYYY_MM_DD_tablename.sql`. This would work, but would make dealing with pull requests and merges annoying, if multiple came in one day. I would suggest a naming scheme more along the lines of `$patchNumber + '_' + $YYYY_MM_DD + '_' + $descriptiveFeatureName`, for example `01_2017_02_03_add_monster_information.sql` and not limiting them to any particular tables. Picking the second naming system will make dealing with pull requests easier and help developers understand what updates are for. Additionally, the leading number provides a good way of tracking our schema revision. | {"url": "https://api.github.com/repos/ACEmulator/ACE/issues/20/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | completed | 79078680 | issue |