Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-4143 Able to export columns data with table structure for only those selected columns like sqlYog
  3. MXS-4883

Extend /sql/:id/queries to return result set metadata

Details

    • Sub-Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 24.02.0
    • REST-API
    • None
    • MXS-SPRINT-194, MXS-SPRINT-195, MXS-SPRINT-196, MXS-SPRINT-197, MXS-SPRINT-199

    Description

      The GUI needs result set metadata like column datatypes, sizes, and the result set's table name to add the "Export as SQL" option. Parsing the query in the GUI was considered but it's not an optimal approach as the users can have multiple "select" in a stored procedure, the GUI can't parse the store procedure to query additional metadata.
      The `mariadb-connector-cpp` seems to have the `ResultSetMetaData` interface, so getting the result set's metadata seems possible.

      Attachments

        Issue Links

          blocks

          New Feature - A new feature of the product, which has yet to be developed. MXS-4143 Able to export columns data with table structure for only those selected columns like sqlYog

          • Major - Major loss of function.
          • Closed

          Activity

            thien.ly Thien Ly added a comment -

            For example:

            {
            		 
               "data":{
            		 
                  "attributes":{
            		 
                     "execution_time":0.00026922799999999999,
            		 
                     "results":[
            		 
                        {
            		 
                           "complete":true,
            		 
                           "data":[
            		 
                              [
            		 
                                 1
            		 
                              ]
            		 
                           ],
            		 
                           "fields":[
            		 
                              "id",
            		 
                              "name"
            		 
                           ],
            		 
                           "attributes":[
            		 
                              "int(11)",
            		 
                              "char(10)"
            		 
                           ],
            		 
                           "table":"t1"
            		 
                        }
            		 
                     ],
            		 
                     "sql":"SELECT id, name FROM test.t1"
            		 
                  }
            		 
               }
            		 
            }

            thien.ly Thien Ly added a comment - For example: { "data":{ "attributes":{ "execution_time":0.00026922799999999999, "results":[ { "complete":true, "data":[ [ 1 ] ], "fields":[ "id", "name" ], "attributes":[ "int(11)", "char(10)" ], "table":"t1" } ], "sql":"SELECT id, name FROM test.t1" } } }

            People

              markus makela markus makela
              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.