Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-16278

Missing DELETE operation in COM_STMT_BULK_STMT

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.2.14, 10.3.6
    • 10.2.20
    • OTHER
    • None

    Description

      Current Bulk command (COM_STMT_BULK_STMT) permit insert, update, but not DELETE operations.

      That is a pain because for JDBC, API permit to indicate if the query will have a resultset or not.
      I don't see any reason for not permitting it.
      One advantage is having only one OK_Packet as a results compared to sending lots of queries with each one having an OK_Packet

      Change is just setting a flag to permit this kind of operation.
      The current result is an error "This command is not supported in the prepared statement protocol yet"

      Attachments

        Issue Links

          Activity

            diego dupin Diego Dupin created issue -
            diego dupin Diego Dupin made changes -
            Field Original Value New Value
            diego dupin Diego Dupin made changes -
            Description Current Bulk command (COM_STMT_BULK_STMT) permit insert, update, but not DELETE operations.

            That is a pain, because for JDBC, API permit to indicate if query will have a resultset or not.
            I don't see any reason for not permitting it, even if not optimized for now.

            Current Bulk command (COM_STMT_BULK_STMT) permit insert, update, but not DELETE operations.

            That is a pain, because for JDBC, API permit to indicate if query will have a resultset or not.
            I don't see any reason for not permitting it, even if not optimized for now.

            Change is just setting a flag to permit this kind of operation.
            Current result is an error "This command is not supported in the prepared statement protocol yet"
            diego dupin Diego Dupin made changes -
            Description Current Bulk command (COM_STMT_BULK_STMT) permit insert, update, but not DELETE operations.

            That is a pain, because for JDBC, API permit to indicate if query will have a resultset or not.
            I don't see any reason for not permitting it, even if not optimized for now.

            Change is just setting a flag to permit this kind of operation.
            Current result is an error "This command is not supported in the prepared statement protocol yet"
            Current Bulk command (COM_STMT_BULK_STMT) permit insert, update, but not DELETE operations.

            That is a pain because for JDBC, API permit to indicate if the query will have a resultset or not.
            I don't see any reason for not permitting it, even if not optimized for now.

            Change is just setting a flag to permit this kind of operation.
            The current result is an error "This command is not supported in the prepared statement protocol yet"
            diego dupin Diego Dupin made changes -
            Affects Version/s 10.2.14 [ 22911 ]
            Affects Version/s 10.2.15 [ 23006 ]
            diego dupin Diego Dupin made changes -
            Description Current Bulk command (COM_STMT_BULK_STMT) permit insert, update, but not DELETE operations.

            That is a pain because for JDBC, API permit to indicate if the query will have a resultset or not.
            I don't see any reason for not permitting it, even if not optimized for now.

            Change is just setting a flag to permit this kind of operation.
            The current result is an error "This command is not supported in the prepared statement protocol yet"
            Current Bulk command (COM_STMT_BULK_STMT) permit insert, update, but not DELETE operations.

            That is a pain because for JDBC, API permit to indicate if the query will have a resultset or not.
            I don't see any reason for not permitting it.
            One advantage is having only one OK_Packet as a results compared to sending lots of queries with each one having an OK_Packet

            Change is just setting a flag to permit this kind of operation.
            The current result is an error "This command is not supported in the prepared statement protocol yet"
            diego dupin Diego Dupin made changes -
            Key MDEV-16276 CONJ-612
            Affects Version/s 10.2.14 [ 22911 ]
            Affects Version/s 10.3.6 [ 23003 ]
            Issue Type Bug [ 1 ] Task [ 3 ]
            Project MariaDB Server [ 10000 ] MariaDB Connector/J [ 10301 ]
            diego dupin Diego Dupin made changes -
            Fix Version/s 2.3.0 [ 22641 ]
            diego dupin Diego Dupin made changes -
            Assignee Oleksandr Byelkin [ sanja ] diego dupin [ diego dupin ]
            diego dupin Diego Dupin made changes -
            Assignee diego dupin [ diego dupin ] Oleksandr Byelkin [ sanja ]
            diego dupin Diego Dupin made changes -
            Fix Version/s 2.3.0 [ 22641 ]
            Key CONJ-612 MDEV-16278
            Issue Type Task [ 3 ] Bug [ 1 ]
            Project MariaDB Connector/J [ 10301 ] MariaDB Server [ 10000 ]
            diego dupin Diego Dupin made changes -
            Affects Version/s 10.3.6 [ 23003 ]
            Affects Version/s 10.2.14 [ 22911 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.2 [ 14601 ]
            georg Georg Richter made changes -
            georg Georg Richter made changes -
            Priority Minor [ 4 ] Critical [ 2 ]
            serg Sergei Golubchik made changes -
            Priority Critical [ 2 ] Major [ 3 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            sanja Oleksandr Byelkin made changes -
            Status Open [ 1 ] In Progress [ 3 ]

            revision-id: a80a08e8e7523203170a26bdef8c4824a3dc9afc (mariadb-10.2.19-51-ga80a08e8e75)
            parent(s): ad3346dddf419aed3e5d16066471fd5022af1795
            author: Oleksandr Byelkin
            committer: Oleksandr Byelkin
            timestamp: 2018-12-13 17:06:26 +0100
            message:

            MDEV-16278: Missing DELETE operation in COM_STMT_BULK_STMT

            Allow array binding for DELETE, test it.

            —

            sanja Oleksandr Byelkin added a comment - revision-id: a80a08e8e7523203170a26bdef8c4824a3dc9afc (mariadb-10.2.19-51-ga80a08e8e75) parent(s): ad3346dddf419aed3e5d16066471fd5022af1795 author: Oleksandr Byelkin committer: Oleksandr Byelkin timestamp: 2018-12-13 17:06:26 +0100 message: MDEV-16278 : Missing DELETE operation in COM_STMT_BULK_STMT Allow array binding for DELETE, test it. —
            sanja Oleksandr Byelkin made changes -
            Assignee Oleksandr Byelkin [ sanja ] Georg Richter [ georg ]
            Status In Progress [ 3 ] In Review [ 10002 ]
            georg Georg Richter added a comment -

            Ok to push

            georg Georg Richter added a comment - Ok to push
            georg Georg Richter made changes -
            Status In Review [ 10002 ] Stalled [ 10000 ]
            sanja Oleksandr Byelkin made changes -
            Assignee Georg Richter [ georg ] Oleksandr Byelkin [ sanja ]
            sanja Oleksandr Byelkin made changes -
            Status Stalled [ 10000 ] In Progress [ 3 ]
            sanja Oleksandr Byelkin made changes -
            Component/s OTHER [ 10125 ]
            Fix Version/s 10.2.20 [ 23212 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 87424 ] MariaDB v4 [ 154419 ]

            People

              sanja Oleksandr Byelkin
              diego dupin Diego Dupin
              Votes:
              0 Vote for this issue
              Watchers:
              5 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.