Walkthrough

Adds a SQL-based DBMS_OUTPUT package and registers it in contrib aggregation; introduces tests and Makefile integration; adds a sample package test and a minor test comment change.

Changes

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant DBMS_OUTPUT
    participant Logger as "RAISE INFO"
    participant Session

    Client->>DBMS_OUTPUT: put_line(text)
    DBMS_OUTPUT->>Logger: RAISE INFO with text
    Logger->>Session: emit output

    Client->>DBMS_OUTPUT: put(text)
    DBMS_OUTPUT->>Logger: RAISE INFO with text
    Logger->>Session: emit output

    Client->>DBMS_OUTPUT: new_line()
    DBMS_OUTPUT->>Logger: RAISE INFO with newline/space
    Logger->>Session: emit output

    Client->>DBMS_OUTPUT: enable(size)
    DBMS_OUTPUT-->>Client: no-op (enabled by default)

    Client->>DBMS_OUTPUT: disable()
    DBMS_OUTPUT-->>Client: no-op (still emits)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Pay attention to:
  • SQL package body correctness and use of RAISE INFO for output.
  • Test script expectations vs actual DBMS_OUTPUT behavior (enable/disable no-ops).
  • Makefile REGRESS integration and test naming.

Suggested reviewers

• OreoYang
• NotHimmel

Poem

🐰 I hopped a line into the tree,
put_line sang loud and true to me.
new_line danced, enable stayed light,
disable slept through day and night.
RAISE INFO echoes — a rabbit's delight! 🥕📢

Pre-merge checks and finishing touches

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Fixed with commit 8f59ead

Hi rophy,
Could you check the failed regression cases below.

Quick tip: You can manually run the regression test by executing the following command in the directory:
highgo@qd:~/works/test/IvorySQL/src/pl/plisql$ make oracle-check

diff -U3 /home/runner/work/IvorySQL/IvorySQL/src/pl/plisql/src/expected/plisql_dbms_output.out /home/runner/work/IvorySQL/IvorySQL/src/pl/plisql/src/results/plisql_dbms_output.out
--- /home/runner/work/IvorySQL/IvorySQL/src/pl/plisql/src/expected/plisql_dbms_output.out	2025-11-18 00:22:58.425668683 +0000
+++ /home/runner/work/IvorySQL/IvorySQL/src/pl/plisql/src/results/plisql_dbms_output.out	2025-11-18 00:36:29.864620493 +0000
@@ -175,12 +175,14 @@
 -- 7. GET_LINES(lines, numlines)  - Retrieve multiple lines from buffer
 --
 -- IvorySQL Current Implementation Status:
--- ✓ PUT_LINE(text)               - Fully working (uses RAISE INFO)
--- ✗ PUT(text)                    - Syntax error
--- ✗ NEW_LINE                     - Syntax error
--- ✗ ENABLE(buffer_size)          - Syntax error
--- ✗ DISABLE                      - Syntax error
+-- ✓ PUT_LINE(text)               - Works (outputs via RAISE INFO)
+-- ✓ PUT(text)                    - Works (outputs via RAISE INFO)
+-- ✗ NEW_LINE                     - Syntax error (no-arg procedure call)
+-- ✓ ENABLE(buffer_size)          - Works (no-op)
+-- ✗ DISABLE                      - Syntax error (no-arg procedure call)
 -- ✗ GET_LINE(line, status)       - Not implemented
 -- ✗ GET_LINES(lines, numlines)   - Not implemented
 --
--- Note: Current implementation outputs immediately (no buffering)
+-- Note:
+-- - Output is immediate (no buffering)
+-- - NEW_LINE and DISABLE fail due to PL/iSQL parser limitation with no-arg procedures

sure, will follow up in a day or two

Hi， Rophy，thanks for your contribution to IvorySQL!
This dbms_output is quite simple. Do you have plan to implement the missing part?

Is aliasing to RAISE INFO good enough?

If that is good enough, I can help to fix those methods such as ENABLE, DISABLE, GET_LINE as no-op.

Otherwise I imagine we will need some buffering mechanism to properly mimic dbms_output

Hi, Rophy, we expect to be compatible with Oracle as possible as we can, so it would be good to implement buffer mechanism and other procedures as well.

That's fair. Feel free to drop this pr.
I'll rework on this once I encounter more dbms_output usages in my testing.

OK, I'll close this PR. Thanks for your contribution to IvorySQl!