Details
-
New Feature
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
Description
Create an ORACLE PACKAGE "DBMS_OUTPUT" that contains the PUT_LINE stored
procedure.
The procedure should take one string argument that should be shown to the users using the command line client (when he has warnings enabled).
We could reuse some of the code for SIGNAL for this task.
Suggested solution:
In addition to implementing the DBMS_OUTPUT.put_line() stored procedure, we also have to implement the functionality for users to generate messages he can view in the command line client.
This is apparently something that some developers uses' everywhere' and we should try to keep the syntax simple. Signal can do part of this, but the syntax is a bit to complex for something that is used over and over again.
[MSG|MESSAGE ] "hello";
This should generate a warning of level 'message' and code 0.
The user would get this in the output in the mariadb client by enable 'warnings', which print out all warnings at the end of each statement.
We could potentially also implement 'show messages' to just show messages.
If we do that, we could add an option to 'mariadb' client to print messages at end of a query.
Attachments
Issue Links
- duplicates
-
-
- Open
-
- is part of
-
MDEV-35973 Oracle Compatibility Project 1 for 2025
-
- In Progress
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue is part of MENT-2216 [ MENT-2216 ] |
| Link | This issue is part of MDEV-19149 [ MDEV-19149 ] |
| Description |
Create an ORACLE PACKAGE "DBMS_OUTPUT" that contains the PUT_LINE stored
procedure. The procedure should take one string argument that should be shown to the users using the command line client (when he has warnings enabled). We could reuse some of the code for SIGNAL for this task Suggested solution: This is apparently something that some developers uses' everywhere' and we should try to keep the syntax simple. Signal can do part of this, but the syntax is a bit to complex for something that is used over and over again. [MSG|MESSAGE ] "hello"; This should generate a warning of level 'message' and code 0. The user would get this in the output in the mariadbdclient by enable 'warnings', which print out all warnings at the end of each statement. We could potentially also implement 'show messages' to just show messages. If we do that, we could add an option to 'mariadb' client to print messages at end of a query. |
Create an ORACLE PACKAGE "DBMS_OUTPUT" that contains the PUT_LINE stored
procedure. The procedure should take one string argument that should be shown to the users using the command line client (when he has warnings enabled). We could reuse some of the code for SIGNAL for this task. Suggested solution: In addition to implementing the DBMS_OUTPUT.put_line() stored procedure, we also have to implement the functionality for users to generate messages he can view in the command line client. This is apparently something that some developers uses' everywhere' and we should try to keep the syntax simple. Signal can do part of this, but the syntax is a bit to complex for something that is used over and over again. [MSG|MESSAGE ] "hello"; This should generate a warning of level 'message' and code 0. The user would get this in the output in the mariadb client by enable 'warnings', which print out all warnings at the end of each statement. We could potentially also implement 'show messages' to just show messages. If we do that, we could add an option to 'mariadb' client to print messages at end of a query. |
| Summary | Procedure DBMS_OUTPUT.PUT_LINE | Procedure DBMS_OUTPUT.PUT_LINE |
| Link | This issue is part of MDEV-35973 [ MDEV-35973 ] |
| Link | This issue is part of MENT-2216 [ MENT-2216 ] |
| Issue Type | Task [ 3 ] | New Feature [ 2 ] |
| Labels | Compatibility | Compatibility Oracle |
| Parent | MDEV-35973 [ 132608 ] | |
| Issue Type | New Feature [ 2 ] | Technical task [ 7 ] |
| Link | This issue is part of MDEV-35973 [ MDEV-35973 ] |
| Link | This issue is part of MDEV-35973 [ MDEV-35973 ] |
| Parent | MDEV-35973 [ 132608 ] | |
| Issue Type | Technical task [ 7 ] | New Feature [ 2 ] |
| Fix Version/s | 12.1 [ 29992 ] | |
| Fix Version/s | 12.0 [ 29945 ] |
| Assignee | Alexander Barkov [ bar ] |
| Component/s | N/A [ 14411 ] | |
| Fix Version/s | N/A [ 14700 ] | |
| Fix Version/s | 12.1 [ 29992 ] | |
| Resolution | Duplicate [ 3 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Link | This issue duplicates MDEV-19149 [ MDEV-19149 ] |
| Link | This issue is part of MDEV-19149 [ MDEV-19149 ] |