On 19 Jun 2003 at 4:15, Ron Johnson wrote:
> One possibility that negates the need for "garbage collection" is
> to create a history table that mirrors the primary table, and
> also has an "activity_code char(1)", with values either "U" or "D".
>
> Then an "before update" or "before delete" trigger would automatically
> insert the pre-update-or-delete record into the history table, along
> with U or D in activity_code.
That makes me think. You can write before insert/before update/before delete
triggers and use dblink in conjunction with that to mimick some kind of
mirroring.
Of course that is bad from keeping transactions in sync. But this remains an
option. If you put remote database connection in async mode in dblink module,
you can reduce the impact of remote operation as well.
HTH
Bye
Shridhar
--
Virtue is a relative term. -- Spock, "Friday's Child", stardate 3499.1
