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

Auto-inject `LIMIT` and `OFFSET`, and allow no limit

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 6.2.1
    • 24.08.0
    • maxgui
    • None
    • MXS-SPRINT-211, MXS-SPRINT-212, MXS-SPRINT-213

    Description

      Hi Team,

      After the SQL LIMIT issue[ MXS-3841 ] is fixed then we have upgraded to 6.2.1 version. But observed the below issue.

      1. Remove the Max Rows option(drop down lis) in the GUI or change it like below SQL yog screenshot option. Can you please change the Max Rows UI to range, like first row and then last row number but default is 0 to 1000/10000. And keep the no limit check box separately if possible.
      NOTE: But don't remove the max_rows=Don't Limit option, please keep it as a separate check box like SQLyog.
      So that user can enter the start value and end value like SQL yog option below.


      Attachments

        Issue Links

          Activity

            People

              thien.ly Thien Ly
              naresh.chandra@copart.com Naresh Chandra
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 24d
                  24d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 13d 5.5h Time Not Required
                  13d 5.5h

                  Git Integration

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