Fix on DB Manager: Get db type from settings and read the settings accordingly #968
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
…e to select the db type. Meanwhile it's recognized from the current projecr or - in this case - recreated from the last used connection (read from the settings) there we need the stored db type and read it then according to it.
gacarrillor
approved these changes
Oct 10, 2024
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.
It was a leftover from the previous functionality where the users have to select the db type. Meanwhile it's recognized from the current projecr or - in this case - recreated from the last used connection (read from the settings) there we need the stored db type and read it then according to it.
It previously leaded to issues when using a PG but reading the setting from MSSQL (even if not installed)...