Fix database prefix #1889
Merged
Fix database prefix #1889
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
Signed-off-by: Jan Vlug <[email protected]>
theCalcaholic
requested changes
Apr 20, 2024
Co-authored-by: Tobias Knöppler <[email protected]> Signed-off-by: Jan Vlug <[email protected]>
theCalcaholic
approved these changes
Apr 22, 2024
theCalcaholic
force-pushed
the
devel
branch
5 times, most recently
from
2a8475f
to
428343e
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 fixes issue #1818 by getting the database prefix from the configuration file and using it in the SQL command that failed because of a hard coded database prefix.