issues: 479416358
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
479416358 | MDU6SXNzdWU0Nzk0MTYzNTg= | 2220 | Remove deleted chars and associated entries from shard db | 37782527 | closed | 0 | 0 | 2019-08-11T21:44:42Z | 2019-09-28T04:01:26Z | 2019-09-28T04:01:26Z | NONE | <!-- IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION YOUR ISSUE MIGHT BE CLOSED WITHOUT INVESTIGATING --> ### Bug Report or Feature Request (mark with an `x`) ``` - [ ] bug report -> please search issues before submitting - [X] feature request ``` ### Desired functionality. This is not a high priority item. More of a wish list sort of feature. Currently when a character is deleted, the character is marked as deleted in the shard db and that's it. The actual entries in the db aren't removed/deleted. What I propose would be a way to remove these deleted characters along with any other associated db entries like biotas / inventory items. This could be done through an SQL file (ran manually against the db by the server operator) or a function builtin to ACE. Being built into ACE, would allow automatic clean up. This would be a configurable option in days that would default to off. So you could set the configuration to say 30 to remove any deleted characters from the db older than 30 days. This would still allow being able to look back at recently deleted characters. The function in ACE would cleanly and properly delete the character and all related entries from the shard db by the date of deletion set by the configurable option. This could either run on server startup or a set interval while the server is running. One thing to consider would be ACE has builtin GUID recycling. So when these entries are deleted from the database, would their GUIDs then be freed to use again? Main reason for this feature would be to reduce the growing size of shard db's on high population servers and to keep the db as efficient as possible. | {"url": "https://api.github.com/repos/ACEmulator/ACE/issues/2220/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | completed | 79078680 | issue |