Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-10764 PL/SQL parser - Phase 2
  3. MDEV-10590

sql_mode=ORACLE: Built-in package DBMS_OUTPUT

Details

    • Technical task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • None
    • N/A
    • OTHER

    Description

      Implement a built-in package DBMS_OUTPUT for sql_mode=ORACLE.
      This feature is actively used by Oracle users, especially for debugging purposes.

      The idea:

      • A stored routine can send debug messages using DBMS_OUTPUT methods, such as DBMS_OUTPUT.PUT_LINE(), which are collected in the package internal buffers.
      • The client program e.g. SQL*Plus retrieves the collected messages using methods such as DBMS_OUTPUT.GET_LINE()

      SQL*Plus understands a special command SET SERVEROUTPUT ON; to enable displaying of the DBMS_OUTPUT messages after each statement executed.

      Example:

      DROP FUNCTION f1;
      		 
      CREATE FUNCTION f1 (a INT) RETURN INT
      		 
      AS
      		 
      BEGIN
      		 
        DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
      		 
        RETURN a;
      		 
      END;
      		 
      /
      		 
      SET SERVEROUTPUT ON;
      		 
      SELECT f1(10) FROM DUAL;


          F1(10)
      		 
      ----------
      		 
      	10
      		 
       
      		 
      a IS 10

      Possible implementation using NOTEs

      When we have MDEV-10591 implemented, we will be able just to create a package DBMS_OUTOUT with a procedure PUT_LINE('string') which will just send 'string' to the client as a NOTE. That would not be exactly the same how Oracle works, but very close, and useful for debugging purposes.

      Attachments

        Issue Links

          duplicates

          New Feature - A new feature of the product, which has yet to be developed. MDEV-19149 System package SYS.DBMS_OUTPUT

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          is blocked by

          Technical task - A technical task. MDEV-10591 Oracle-style packages

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            bar Alexander Barkov created issue -
            bar Alexander Barkov made changes -
            Field Original Value New Value
            Description Implement a built-in package {{DBMS_OUTPUT}} for {{sql_mode=ORACLE}}.
            This feature is actively used by Oracle users, especially for debugging purposes.

            The idea:
            - A stored routine can send debug messages using {{DBMS_OUTPUT}} methods, such as {{DBMS_OUTPUT.PUT_LINE()}}, which is collected in the package internal buffers.
            - The client program e.g. {{SQL*Plus}} retrieves the collected information using methods such as {{DBMS_OUTPUT.GET_LINE()}}

            {{SQL*Plus}} understands a special command {{SET SERVEROUTPUT ON;}} to enable displaying of the {{DBMS_OUTPUT}} messages after each statement executed.

            Example:
            {code:sql}
            DROP FUNCTION f1;
            CREATE FUNCTION f1 (a INT) RETURN INT
            AS
            BEGIN
              DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
              RETURN a;
            END;
            /
            SET SERVEROUTPUT ON;
            SELECT f1(10) FROM DUAL;
            {code}
            {noformat}
                F1(10)
            ----------
            10

            a IS 10
            {noformat}
            		Implement a built-in package {{DBMS_OUTPUT}} for {{sql_mode=ORACLE}}.
            This feature is actively used by Oracle users, especially for debugging purposes.

            The idea:
            - A stored routine can send debug messages using {{DBMS_OUTPUT}} methods, such as {{DBMS_OUTPUT.PUT_LINE()}}, which are collected in the package internal buffers.
            - The client program e.g. {{SQL*Plus}} retrieves the collected messages using methods such as {{DBMS_OUTPUT.GET_LINE()}}

            {{SQL*Plus}} understands a special command {{SET SERVEROUTPUT ON;}} to enable displaying of the {{DBMS_OUTPUT}} messages after each statement executed.

            Example:
            {code:sql}
            DROP FUNCTION f1;
            CREATE FUNCTION f1 (a INT) RETURN INT
            AS
            BEGIN
              DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
              RETURN a;
            END;
            /
            SET SERVEROUTPUT ON;
            SELECT f1(10) FROM DUAL;
            {code}
            {noformat}
                F1(10)
            ----------
            10

            a IS 10
            {noformat}
            bar Alexander Barkov made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            monty Michael Widenius made changes -
            Parent MDEV-10142 [ 56873 ]
            Issue Type Task [ 3 ] Technical task [ 7 ]
            bar Alexander Barkov made changes -
            Description Implement a built-in package {{DBMS_OUTPUT}} for {{sql_mode=ORACLE}}.
            This feature is actively used by Oracle users, especially for debugging purposes.

            The idea:
            - A stored routine can send debug messages using {{DBMS_OUTPUT}} methods, such as {{DBMS_OUTPUT.PUT_LINE()}}, which are collected in the package internal buffers.
            - The client program e.g. {{SQL*Plus}} retrieves the collected messages using methods such as {{DBMS_OUTPUT.GET_LINE()}}

            {{SQL*Plus}} understands a special command {{SET SERVEROUTPUT ON;}} to enable displaying of the {{DBMS_OUTPUT}} messages after each statement executed.

            Example:
            {code:sql}
            DROP FUNCTION f1;
            CREATE FUNCTION f1 (a INT) RETURN INT
            AS
            BEGIN
              DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
              RETURN a;
            END;
            /
            SET SERVEROUTPUT ON;
            SELECT f1(10) FROM DUAL;
            {code}
            {noformat}
                F1(10)
            ----------
            10

            a IS 10
            {noformat}
            		Implement a built-in package {{DBMS_OUTPUT}} for {{sql_mode=ORACLE}}.
            This feature is actively used by Oracle users, especially for debugging purposes.

            The idea:
            - A stored routine can send debug messages using {{DBMS_OUTPUT}} methods, such as {{DBMS_OUTPUT.PUT_LINE()}}, which are collected in the package internal buffers.
            - The client program e.g. {{SQL*Plus}} retrieves the collected messages using methods such as {{DBMS_OUTPUT.GET_LINE()}}

            {{SQL*Plus}} understands a special command {{SET SERVEROUTPUT ON;}} to enable displaying of the {{DBMS_OUTPUT}} messages after each statement executed.

            Example:
            {code:sql}
            DROP FUNCTION f1;
            CREATE FUNCTION f1 (a INT) RETURN INT
            AS
            BEGIN
              DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
              RETURN a;
            END;
            /
            SET SERVEROUTPUT ON;
            SELECT f1(10) FROM DUAL;
            {code}
            {noformat}
                F1(10)
            ----------
            10

            a IS 10
            {noformat}


            When we have MDEV-10591 implemented, we will be able just to create a package {{DBMS_OUTOUT}} with a procedure PUT_LINE('string') which will just send 'string' to the client as a NOTE. That would not be exactly the same how Oracle works, but very close.
            bar Alexander Barkov made changes -
            Description Implement a built-in package {{DBMS_OUTPUT}} for {{sql_mode=ORACLE}}.
            This feature is actively used by Oracle users, especially for debugging purposes.

            The idea:
            - A stored routine can send debug messages using {{DBMS_OUTPUT}} methods, such as {{DBMS_OUTPUT.PUT_LINE()}}, which are collected in the package internal buffers.
            - The client program e.g. {{SQL*Plus}} retrieves the collected messages using methods such as {{DBMS_OUTPUT.GET_LINE()}}

            {{SQL*Plus}} understands a special command {{SET SERVEROUTPUT ON;}} to enable displaying of the {{DBMS_OUTPUT}} messages after each statement executed.

            Example:
            {code:sql}
            DROP FUNCTION f1;
            CREATE FUNCTION f1 (a INT) RETURN INT
            AS
            BEGIN
              DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
              RETURN a;
            END;
            /
            SET SERVEROUTPUT ON;
            SELECT f1(10) FROM DUAL;
            {code}
            {noformat}
                F1(10)
            ----------
            10

            a IS 10
            {noformat}


            When we have MDEV-10591 implemented, we will be able just to create a package {{DBMS_OUTOUT}} with a procedure PUT_LINE('string') which will just send 'string' to the client as a NOTE. That would not be exactly the same how Oracle works, but very close.
            		Implement a built-in package {{DBMS_OUTPUT}} for {{sql_mode=ORACLE}}.
            This feature is actively used by Oracle users, especially for debugging purposes.

            The idea:
            - A stored routine can send debug messages using {{DBMS_OUTPUT}} methods, such as {{DBMS_OUTPUT.PUT_LINE()}}, which are collected in the package internal buffers.
            - The client program e.g. {{SQL*Plus}} retrieves the collected messages using methods such as {{DBMS_OUTPUT.GET_LINE()}}

            {{SQL*Plus}} understands a special command {{SET SERVEROUTPUT ON;}} to enable displaying of the {{DBMS_OUTPUT}} messages after each statement executed.

            Example:
            {code:sql}
            DROP FUNCTION f1;
            CREATE FUNCTION f1 (a INT) RETURN INT
            AS
            BEGIN
              DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
              RETURN a;
            END;
            /
            SET SERVEROUTPUT ON;
            SELECT f1(10) FROM DUAL;
            {code}
            {noformat}
                F1(10)
            ----------
            10

            a IS 10
            {noformat}



            When we have MDEV-10591 implemented, we will be able just to create a package {{DBMS_OUTOUT}} with a procedure {{PUT_LINE('string')}} which will just send {{'string'}} to the client as a {{NOTE}}. That would not be exactly the same how Oracle works, but very close, and useful for debugging purposes.

            bar Alexander Barkov made changes -
            Description Implement a built-in package {{DBMS_OUTPUT}} for {{sql_mode=ORACLE}}.
            This feature is actively used by Oracle users, especially for debugging purposes.

            The idea:
            - A stored routine can send debug messages using {{DBMS_OUTPUT}} methods, such as {{DBMS_OUTPUT.PUT_LINE()}}, which are collected in the package internal buffers.
            - The client program e.g. {{SQL*Plus}} retrieves the collected messages using methods such as {{DBMS_OUTPUT.GET_LINE()}}

            {{SQL*Plus}} understands a special command {{SET SERVEROUTPUT ON;}} to enable displaying of the {{DBMS_OUTPUT}} messages after each statement executed.

            Example:
            {code:sql}
            DROP FUNCTION f1;
            CREATE FUNCTION f1 (a INT) RETURN INT
            AS
            BEGIN
              DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
              RETURN a;
            END;
            /
            SET SERVEROUTPUT ON;
            SELECT f1(10) FROM DUAL;
            {code}
            {noformat}
                F1(10)
            ----------
            10

            a IS 10
            {noformat}



            When we have MDEV-10591 implemented, we will be able just to create a package {{DBMS_OUTOUT}} with a procedure {{PUT_LINE('string')}} which will just send {{'string'}} to the client as a {{NOTE}}. That would not be exactly the same how Oracle works, but very close, and useful for debugging purposes.

            		Implement a built-in package {{DBMS_OUTPUT}} for {{sql_mode=ORACLE}}.
            This feature is actively used by Oracle users, especially for debugging purposes.

            The idea:
            - A stored routine can send debug messages using {{DBMS_OUTPUT}} methods, such as {{DBMS_OUTPUT.PUT_LINE()}}, which are collected in the package internal buffers.
            - The client program e.g. {{SQL*Plus}} retrieves the collected messages using methods such as {{DBMS_OUTPUT.GET_LINE()}}

            {{SQL*Plus}} understands a special command {{SET SERVEROUTPUT ON;}} to enable displaying of the {{DBMS_OUTPUT}} messages after each statement executed.

            Example:
            {code:sql}
            DROP FUNCTION f1;
            CREATE FUNCTION f1 (a INT) RETURN INT
            AS
            BEGIN
              DBMS_OUTPUT.PUT_LINE('a IS '||TO_CHAR(a));
              RETURN a;
            END;
            /
            SET SERVEROUTPUT ON;
            SELECT f1(10) FROM DUAL;
            {code}
            {noformat}
                F1(10)
            ----------
            10

            a IS 10
            {noformat}


            h2. Possible implementation using NOTEs
            When we have MDEV-10591 implemented, we will be able just to create a package {{DBMS_OUTOUT}} with a procedure {{PUT_LINE('string')}} which will just send {{'string'}} to the client as a {{NOTE}}. That would not be exactly the same how Oracle works, but very close, and useful for debugging purposes.

            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility
            serg Sergei Golubchik made changes -
            Labels Compatibility
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility Compatibility NRE-307517
            alvinr Alvin Richards (Inactive) made changes -
            NRE Projects NRE-307517
            alvinr Alvin Richards (Inactive) made changes -
            Labels Compatibility NRE-307517 Compatibility
            bar Alexander Barkov made changes -
            Fix Version/s 10.3 [ 22126 ]
            Fix Version/s 10.2 [ 14601 ]
            elenst Elena Stepanova made changes -
            Comment [ Should it have 10.2 as a fix version? ]
            alvinr Alvin Richards (Inactive) made changes -
            Parent MDEV-10142 [ 56873 ] MDEV-10764 [ 57940 ]
            serg Sergei Golubchik made changes -
            Fix Version/s 10.3 [ 22126 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            Support case ID not-26307
            ralf.gebhardt Ralf Gebhardt made changes -
            NRE Projects AC-2610/DEFERRED
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 76696 ] MariaDB v4 [ 140041 ]
            julien.fritsch Julien Fritsch made changes -
            Assignee Alexander Barkov [ bar ]
            julien.fritsch Julien Fritsch made changes -
            Fix Version/s 12.2 [ 30146 ]
            bar Alexander Barkov made changes -
            Fix Version/s N/A [ 14700 ]
            Fix Version/s 12.2 [ 30146 ]
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Closed [ 6 ]
            bar Alexander Barkov made changes -

            People

              bar Alexander Barkov
              bar Alexander Barkov
              Votes:
              4 Vote for this issue
              Watchers:
              8 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.