Re: Handling Record Change Journal Entries -- MIDRANGE-L

Subject: Re: Handling Record Change Journal Entries
From: "D*B" <dieter.bender@xxxxxxxxxxxx>
Date: Sat, 5 Jan 2019 20:35:06 +0100
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

<J.O.>
Triggers in and of themselves do not ensure transaction integrity, they complicate it.
</J.O.>

... for transaction safety, you would need commitment controll anyway and making updates without cc is not state of the art. Ensuring transaction safety with the requiremnet of synchronous replication is in deed rather complicated and I didn't want to elaborate on this, before the requirements are well defined...

Dieter

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.