issue_comments: 280639466
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/pull/36#issuecomment-280639466 | https://api.github.com/repos/ACEmulator/ACE/issues/36 | 280639466 | MDEyOklzc3VlQ29tbWVudDI4MDYzOTQ2Ng== | 25387933 | 2017-02-17T12:43:40Z | 2017-02-17T12:43:40Z | CONTRIBUTOR | Hi Mag-nus, The problem with your idea is some asshat will figure out how to screw up their original db. I worked on many production level database patches and they pretty much all start at step x and move forward where x can be the current software version. Your right as a new installer needs to run from version 0 and then if version 50 removes a table in version 0 it will be a useless step and take more time. But the benefits of the system far outweigh the useless garbage. With a design that goes by version and up you can guarantee that the database is always standard and it eliminates the room for error with things getting out of sync or even missed. When you have the step process it's a little more work and sometimes seems dumb but it keeps all the db updates on a forward track even if they seem to be doing things the slow way. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 205449659 |