Re: Database I/O Modernization -- 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: Database I/O Modernization
From: "D*B" <dieter.bender@xxxxxxxxxxxx>
Date: Fri, 15 Sep 2017 20:51:00 +0200
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>

<Nathan>
I'm just saying that there are valid use cases for SQL, and that there just as valid
use cases for RLA. Pick the right tool for the job.
</Nathan>

May I remind you about the topic, we are discussing: "Database I/O Modernization"!!! It was your choice, not mine. RLA might be the right tool for some job (I suspect it is) but it is by far not the right tool for Database modernisation!!!

D*B

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.