-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Crashin' Thrashin' Battleship attempts on load #824
base: master
Are you sure you want to change the base?
Conversation
This item had a typo in its name (extra parenthesis). While splitting the holiday events database, the typo was fixed. Unfortunately that means anyone who had attempts recorded under the old name would suddenly find them missing. The easy way around this would be to just restore the old name and leave it unchanged, forever. But there are some other items that would benefit from a migration system: Firstly, the "Big Love Rocket" is no longer named that, and then there's the manual "purge" command for Island Expedition items that never made it to live. Whether this approach is right, I've no idea. The migration logic is extremely basic so as to avoid destroying any data. Keeping in mind there are no tests for this yet, it does seem like the safest route. Eventually there may be tests and then this functionality can be extended. For now, I'd rather not mess with the DB internals any more than necessary, especially because many people don't seem to create any backups.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like a good solution.
We'll of course have to do this manually for all items that needs to be migrated but that shouldn't happen too often.
This typo was fixed when splitting the holiday items database, but previous attempts would have been stored under the old (incorrect) name. I don't have time to refine the WIP migration PR (#824) before the next release, so it's probably better to restore the original name and fix the database up properly later. Players will only see the localized name, which doesn't contain the typo. Fixing the name is of moderate utility at best and can be deferred. I'd rather not merge a somewhat half-baked DB migration feature before I've spent more time on refining and testing it.
This typo was fixed when splitting the holiday items database, but previous attempts would have been stored under the old (incorrect) name. I don't have time to refine the WIP migration PR (#824) before the next release, so it's probably better to restore the original name for the time being, and take all the time needed to fix the database up properly later. Players will only see the localized name, which doesn't contain the typo. Fixing the name is of moderate utility at best and can be deferred. I'd rather not merge a half-baked DB migration feature before I've spent more time on refining and testing it.
This typo was fixed when splitting the holiday items database (in b2b1f30), but previous attempts would have been stored under the old (incorrect) name. I don't have time to refine the WIP migration PR (#824) before the next release, so it's probably better to restore the original name for the time being, and take all the time needed to fix the database up properly later. Players will only see the localized name, which doesn't contain the typo. Fixing the name is of moderate utility at best and can be deferred. I'd rather not merge a half-baked DB migration feature before I've spent more time on refining and testing it.
Thanks for the review! I've decided to postpone adding this feature as it would benefit from more refinement (and testing). |
This item had a typo in its name (extra parenthesis). While splitting the holiday events database, the typo was fixed. Unfortunately that means anyone who had attempts recorded under the old name would suddenly find them missing.
The easy way around this would be to just restore the old name and leave it unchanged, forever. But there are some other items that would benefit from a migration system: Firstly, the "Big Love Rocket" is no longer named that, and then there's the manual "purge" command for Island Expedition items that never made it to live. Whether this approach is right, I've no idea.
The migration logic is extremely basic so as to avoid destroying any data. Keeping in mind there are no tests for this yet, it does seem like the safest route. Eventually there may be tests and then this functionality can be extended. For now, I'd rather not mess with the DB internals any more than necessary, especially because many people don't seem to create any backups.
Status: Shelved for now. Needs automated testing, which requires some other database work to be completed first.