Some users of PL/Java make use of a non-default connection from within a Trigger in order to
do this. In essence, they load the client JDBC package into the backend to let the backend
as such become a client. The second connection is then maintained for the lifetime of the
first. Perhaps not the most efficient way of doing it but it works.
Regards,
Thomas Hallgren
Gurjeet Singh wrote:
Do we have any plans of introducing 'AUTONOMOUS TRANSACTION' like
feature?
Again, it might not be a part of the standard.... but it is very
helpful in situations like these!!! You can run a trigger with an
autonomous transaction attached to it, which guarantees that the work
done by trigger persists even though the calling transaction rolls
back (potentially a hacker trying to cover his tracks)!!!
(http://asktom.oracle.com/~tkyte/autonomous/index.html)
Gurjeet.
On 5/16/06, Josh Berkus <josh@agliodbs.com> wrote:
Doug,
> But what if the user calls the access function, sees the data, then
> issues a ROLLBACK? The audit record would be rolled back as well (as
> Tom pointed out earlier).
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
