| DBMS_OUTPUT and .NET client code [message #81200] |
Wed, 22 January 2003 08:22  |
Mike Nibeck
Messages: 49
Registered: May 2002
|
Member |
|
|
Does anyone know of anyway to capture the DBMS_OUTPUT buffer contents from a .NET connected piece of code. We are developing in .NET, and it would be real usefull if we could see the DBMS_OUTPUT that our stored procs are genereating for debugging purposes. TOAD can capture and display this, so I image that it's possible.
- Mike
|
|
|
|
| Re: DBMS_OUTPUT and .NET client code [message #81205 is a reply to message #81200] |
Wed, 22 January 2003 16:01  |
Stefan Mueller
Messages: 11
Registered: January 2002
|
Junior Member |
|
|
it's also in the DBMS_OUTPUT package!
here's a description of this package procedure:
PROCEDURE get_line(line OUT VARCHAR2, status OUT INTEGER);
-- Get a single line back that has been buffered. The lines are
-- delimited by calls to put_line or new_line. The line will be
-- constructed taking all the items up to a newline, converting all
-- the items to varchar2, and concatenating them into a single line.
-- If the client fails to retrieve all lines before the next put,
-- put_line or new_line, the non-retrieved lines will be discarded.
-- This is so if the client is interrupted while selecting back
-- the information, there will not be junk left over which would
-- look like it was part of the NEXT set of lines.
-- Output parameters:
-- line
-- This line will hold the line - it may be up to 255 bytes long.
-- status
-- This will be 0 upon successful completion of the call. 1 means
-- that there are no more lines.
Cheers, Stefan
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
