Re: Dreaded PLS-123 Error

From: "Jared Still" <jkstill@xxxxxxxxx>
To: post.ethan@xxxxxxxxx
Date: Thu, 16 Nov 2006 11:01:43 -0800

On 11/9/06, Ethan Post <post.ethan@xxxxxxxxx> wrote:


Thanks, we can not do that because it is not that much variety of code,
just a column by column check for changing values which then goes to audit
log table if value is changing. However, that is good to know, I was not
aware that the limits were different.



Why not?

Create index-by table in the trigger, populate it with new/old values,
send the index-by table as a parameter to the package.

--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

Follow-Ups:

Re: Dreaded PLS-123 Error
From: Jared Still

References:
- Dreaded PLS-123 Error
  - From: Ethan Post
- Re: Dreaded PLS-123 Error
  - From: Gints Plivna
- Re: Dreaded PLS-123 Error
  - From: Ethan Post

Other related posts:

Browse oracle-l