Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4789

GUI workspace caching doesn't work accurately

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 23.08.4
    • maxgui
    • None
    • MXS-SPRINT-191, MXS-SPRINT-192

    Description

      Caching in the workspace doesn't work as expected. Computed properties data based on the active worksheet or query tab ID changes even when the component is kept inactive.
      To resolve this issue, the ID must be passed via props and computed properties should get data based on this ID instead of getting data from the active ID

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MXS-4728 Laggy issues on result data table

          • Major - Major loss of function.
          • Closed
          causes

          Bug - A problem which impairs or prevents the functions of the product. MXS-4855 While writing query GUI response very slow

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MXS-5221 Query Editor: Unable to visualize preview data result set

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MXS-5222 Query Editor: Unable to fully see error result when previewing a table

          • Major - Major loss of function.
          • Closed

          Activity

            People

              thien.ly Thien Ly
              thien.ly Thien Ly
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.