Re: pipes

Hi Rowan,

We had the same problem, we solved it with the TABLE-type that comes with PL/SQL version 2.

We created a procedure ???_COMMIT, the first thing to do within this procedure
is to make a TABLE-type (for example SAVE_LOG) of the same structure as your LOG-table.
Then fill this table (SAVE_LOG) with the data from your LOG-table, now it's save
to rollback. Then do the opposite action, fill your LOG-table with the data from SAVE_LOG
now do a commit.
Everything has been rollbacked, except your LOG-table.

Greetings Eric

Business Information Services <email_at_bisinfo.com.au> wrote in article <MPG.ddbf7b5acc1421e989694_at_nsw-newshost.tpgi.com.au>...
> Hi there,
>
> I want to set up an error log. I have a table called log and a table
> called transaction. When a transaction comes in I do all this stuff that
> I won't bore you with, but basically it updates various other tables in
> the database.
>
> If any of it goes wrong I want to rollback the changes to the database
> but I do not want to roll back the entries that have been written to the
> log table.
>
> Currently what happens is that all changes to the database including the
> LOG table are rolled back.
>
> I have done some reading and have found a package called DBMS_PIPE which
> the writer says is useful for this situation. Unfortunately he doesn't
> say how.
>
> Does anyone know how or can help with other suggestions?
>
> Regards,
> Rowan McCammon.
> --
> Business Information Services
> (For more information call Brad Deveson)
>
> Tel: (02) 9387-2509 (Australia)
> Fax: (02) 9369-3840 (Australia)
> mailto:email_at_bisinfo.com.au
> http://www.bisinfo.com.au
>
Received on Thu May 08 1997 - 00:00:00 CDT