Re: 10.2.0.1 trace uncommitted inserts
From: ddf <oratune_at_msn.com>
Date: Fri, 29 Apr 2011 13:15:11 -0700 (PDT)
Message-ID: <dbd152c0-1b1f-4685-9a31-cf71e82485d0_at_m10g2000yqd.googlegroups.com>
On Apr 29, 12:47 pm, John Hurley <hurleyjo..._at_yahoo.com> wrote:
> Mladen:
>
> # Now this looks like an intelligent design! There are entities called
> "triggers" which can be made to fire on insert.
>
> ...
>
> So you have already been able to look inside from the little material
> supplied by the OP and guess that triggers are involved? Your crystal
> ball must be working better than mine today.
Date: Fri, 29 Apr 2011 13:15:11 -0700 (PDT)
Message-ID: <dbd152c0-1b1f-4685-9a31-cf71e82485d0_at_m10g2000yqd.googlegroups.com>
On Apr 29, 12:47 pm, John Hurley <hurleyjo..._at_yahoo.com> wrote:
> Mladen:
>
> # Now this looks like an intelligent design! There are entities called
> "triggers" which can be made to fire on insert.
>
> ...
>
> So you have already been able to look inside from the little material
> supplied by the OP and guess that triggers are involved? Your crystal
> ball must be working better than mine today.
That is not what Mladen said or implied. The intent here is to suggest that the OP possibly create a trigger to capture insert transactions into a separate table, with other information such as who did the insert and when, to track what is or isn't happening. There was no mention that the venedor is using triggers.
David Fitzjarrell Received on Fri Apr 29 2011 - 15:15:11 CDT