Re: Data Corruption / 400 -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Data Corruption / 400
From: "Leif Svalgaard" <leif@xxxxxxxxxxxxx>
Date: Mon, 8 Apr 2002 15:57:08 -0500
List-archive: <http://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: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

From: Joe Pluta <joepluta@PlutaBrothers.com>
> > why Al, what other reasons could there be than one of the above?
>
> Loss of "database synchronization" leading to a "database rebuild"
operation
> which "loses recent transactions".  In other words, a bug in the database
> software that causes data to be improperly stored

among Al's "other than" causes was "software bugs". What you refer to
is a software bug (or is "a bug in the database software" not a "software
bug"?)

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Data Corruption / 400 , Joe Pluta

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.