Re: Database I/O Modernization -- MIDRANGE-L

Subject: Re: Database I/O Modernization
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Fri, 15 Sep 2017 09:55:04 -0400
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>

On 9/14/2017 6:26 PM, Nathan Andelin wrote:

Now that the original file is referenced in hundreds, or perhaps thousands
of programs, the cost of changing the design would probably be very high.
Would it have helped if SQL had been used instead of "F" specs?

In the F-spec scenario, we are forced to edit, recompile, and test every
single program using the master file.

In the SQL scenario, we only (only, ha!) need to recompile the subset of
programs which use the refactored columns in some way.

I myself find that helpful.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Database I/O Modernization , Nathan Andelin

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.