[MXS-4364] Query Tab is not selecting the Default schema which already selected in the First Query Tab Created: 2022-10-25 Updated: 2023-08-14 Resolved: 2023-08-14 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | maxgui |
| Affects Version/s: | 22.08.2 |
| Fix Version/s: | 23.08.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Naresh Chandra | Assignee: | Duong Thien Ly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-188 | ||||||||
| Description |
|
After creating a First Query Tab and selecting some xyz schema and ran some queries, so if we create a second Query Tab or 3rd Tab then it's not using the same xyz schema (Which we already selected/used schema in the First Query Tab) automatically and. It means when we try to create a new query tab's after creating a first tab then again, we have to select the schema for the new query tabs. |
| Comments |
| Comment by Duong Thien Ly [ 2022-10-26 ] |
|
This is an expected behavior. When you create a new query tab, you're creating a new thread. On this new thread, the active schema will be null by default. This gives the user ability to run queries on a different schema (database). |
| Comment by Duong Thien Ly [ 2022-10-26 ] |
|
I'll change it to a feature request as this is an expected behavior. |