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

DROP SERVER IF EXISTS doesn't issue a warning if server not exists

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 10.1(EOL)
    • 10.1(EOL)
    • None
    • None

    Description

      MariaDB KB doesn't describe the behavior of DROP SERVER IF EXISTS, so I expect it to work like DROP TABLE IF EXISTS. Which means that IF EXISTS should return a warning if the server doesn't exists. However, this is not the case:

      MariaDB [(none)]> DROP SERVER IF EXISTS not_exists;
      		 
      Query OK, 0 rows affected (0.01 sec)
      		 
       
      		 
      MariaDB [(none)]> SHOW WARNINGS;
      		 
      Empty set (0.00 sec)
      		 
       
      		 
      MariaDB [(none)]> DROP SERVER not_exists;          
      ERROR 1477 (HY000): The foreign server name you are trying to reference does not exist. Data source error:  not_exists

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          f_razzoli Federico Razzoli created issue -
          f_razzoli Federico Razzoli added a comment -

          I didn't check other IF [NOT] EXISTS clauses, so I don't know if the bug is only about DROP SERVER.

          f_razzoli Federico Razzoli added a comment - I didn't check other IF [NOT] EXISTS clauses, so I don't know if the bug is only about DROP SERVER.
          serg Sergei Golubchik made changes -
          Field Original Value New Value
          Priority Trivial [ 5 ] Minor [ 4 ]
          elenst Elena Stepanova made changes -
          Status Open [ 1 ] Confirmed [ 10101 ]
          elenst Elena Stepanova added a comment -

          Thanks for the report.

          As far as I can tell, it's the only object which does not trigger the warning.

          I don't see anything in MDEV-5359 or MDEV-7285 that would explain it. There is an MTR test main.create_drop_server which covers this functionality, and its result file does not have the warning either; but I'm still not sure it's intentional.

          Assigning to bar, he will know.

          elenst Elena Stepanova added a comment - Thanks for the report. As far as I can tell, it's the only object which does not trigger the warning. I don't see anything in MDEV-5359 or MDEV-7285 that would explain it. There is an MTR test main.create_drop_server which covers this functionality, and its result file does not have the warning either; but I'm still not sure it's intentional. Assigning to bar , he will know.
          elenst Elena Stepanova made changes -
          Fix Version/s 10.1 [ 16100 ]
          Assignee Alexander Barkov [ bar ]
          greenman Ian Gilfillan added a comment -

          I've added a mention of this anomalous behaviour to the docs in the meantime:
          https://mariadb.com/kb/en/mariadb/drop-server/+revision/56011/56010/

          greenman Ian Gilfillan added a comment - I've added a mention of this anomalous behaviour to the docs in the meantime: https://mariadb.com/kb/en/mariadb/drop-server/+revision/56011/56010/
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 73619 ] MariaDB v4 [ 143865 ]

          People

            bar Alexander Barkov
            f_razzoli Federico Razzoli
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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