[WIP] Redesign database infrastructure #912
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All tables that have an `(account_id, game_id)` primary key will be changed to `(player_id, game_id)`. Pretty much every instance of an account ID is replaced with a player ID in all game-scoped code. This is the first step in a major redesign to associate tables to the most closely-related table, rather than having everything depend on the high-level `account` table. Some features that this change will help facilitate: * Multiple players per account per game (to replace "multi accounts"). * NPCs not needing an associated account. * Free-standing ships/weapons.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All tables that have an
(account_id, game_id)primary key will bechanged to
(player_id, game_id). Pretty much every instance of anaccount ID is replaced with a player ID in all game-scoped code.
This is the first step in a major redesign to associate tables to the
most closely-related table, rather than having everything depend on
the high-level
accounttable.Some features that this change will help facilitate: