WIP: Refactor server database #6263
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
Krzmbrzl
force-pushed
the
refac-database
branch
5 times, most recently
from
a26dd78
to
28acdc8
Compare
Krzmbrzl
force-pushed
the
refac-database
branch
from
80c18a6
to
554762f
Compare
Krzmbrzl
force-pushed
the
refac-database
branch
2 times, most recently
from
2a149e9
to
825b6b1
Compare
Krzmbrzl
force-pushed
the
refac-database
branch
3 times, most recently
from
a0b5044
to
0cff06a
Compare
Krzmbrzl
force-pushed
the
refac-database
branch
2 times, most recently
from
3584ad3
to
62ac5fc
Compare
Krzmbrzl
force-pushed
the
refac-database
branch
9 times, most recently
from
8c00f1f
to
811cfa6
Compare
Krzmbrzl
force-pushed
the
refac-database
branch
2 times, most recently
from
de96b46
to
5c928be
Compare
Each supported backend can be excluded from the build separately
The dumped JSON format may not be 100% DB backend independent but it should be somewhat close to it. Implements mumble-voip#4980 Implements mumble-voip#2960 (must be done manually though)
Mumble treats usernames case-insensitively. However, in the server, there is a cache that maps usernames to IDs of registered users. We do lazy loading so when a given name is not yet in the cache, we check the database for a match and if that returns something, we insert the result into the cache. However, the DB does case-insensitive lookups whereas the cache used to be case-sensitive. Therefore, different casings of the same username could end up in the cache (all pointing to the same user ID). If that user got unregistered, only one of the possible ways of writing their name gets removed from the cache, leaving the other entries (which are now stale) untouched. This can cause problems when another user now wants to register with a name that corresponds to one of those stale cache entries. The server will think that the given username is already taken, ensuring leading to a rejection of the registration request. A server restart purges the stale entries from the cache. This commit ensures that the cache is now also operating in a case-insensitive manner such that we shouldn't ever create any duplicate entries in there in the first place. Fixes mumble-voip#6383
Krzmbrzl
force-pushed
the
refac-database
branch
13 times, most recently
from
585b01c
to
3483eb4
Compare
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.
This PR completely rewrites the database handling on the server side. In so doing it cleans up and unifies the mess of the current implementation and adds proper unit testing support - in particular for data migration paths, which should provide an overall more reliable experience for users as the tests more or less guarantee that the data migration will work as intended. Additionally, since unit tests are run against all supported backends (SQLite, MySQL, PostgreSQL), all should work equally fine (at least from a functionality point of view).
As a bonus, the dependence on Qt for the database handling is completely removed. Instead, the new framework is built on SOCI.
This PR should address the following issues:
Checks