Re: SERVEROUTPUT Status

Daniel,

Daniel Morgan <damorgan_at_x.washington.edu> wrote
> DBMS_OUTPUT does not belong in production code: Ever!

I think it's wrong. Like probably the most of the statements with the word 'ever'. DBMS_OUTPUT has two main restrictions: buffer size and line size. They are not a reason not to use it though. Ever! :) If your output fits in, it's the easiest way to go.

The output doesn't disappear in nowhere, normally it goes to a logfile. And Syltrem did mention this. I don't know where you get your 'A simple "clear screen" and your record is gone' from.

> INSERT INTO <table_name> is overkill?

You need:
- create table and indexes
- code autonomous transaction if there is need for non-transactional output

- grant privileges
- define, code and monitor purge procedure
- provide easy access to the log table (reports, views).

All these instead of dbms_output.put_line, which gives the same result and the same persistency.

I'm not saying use dbms_output when ever you need the output from pl/sql. But it's quite appropriate in the Syltrem's situation.

Regards,
Igor Received on Thu Feb 12 2004 - 00:35:39 CST