Re: Why file journaling requirement for SQL operations? -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Why file journaling requirement for SQL operations?
From: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Date: Fri, 14 May 2021 10:16:10 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Heh! I knew there was some reason!

On 5/14/2021 10:02 AM, Rob Berendt wrote:

Vern,
The problem is that "just turn on CC" involves changing a few million lines of code in a full blown ERP package you may, or may not, have the source to. So, even if you can do that, do you want to go through such a change management process? And repeat it upon every vendor upgrade?
Much more cost effective to add on the journal option.

Rob Berendt

This mailing list archive is Copyright 1997-2026 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.