Fix database selection translation issue (#799)Fix database selection translation issue (#799)Fix database selection translation issue (#799) #810
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.
Summary
Fixes issue #799 where database selection options were not translated when users switched languages.
Changes
en.js.Workspace.jsxto use the i18n translation function (t()) for database names and the generic description.db_transactsqlis used for MSSQL.Testing
Closes #799- Add translation keys for all database names (MySQL, PostgreSQL, SQLite, MariaDB, MSSQL, Oracle SQL)
Fixes #799### Summary
Fixes issue #799 where database selection options were not translated when users switched languages.
Changes
en.js.Workspace.jsxto use the i18n translation function (t()) for database names and the generic description.db_transactsqlis used for MSSQL.Testing
Closes #799