×
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.
RLA is only good for transaction processing if your transaction spans only one record so you don't care about commitment control. If you need to rollback a transaction distributed across multiple tables on multiple systems, RLA is really icky.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Tuesday, May 14, 2013 3:38 PM
To: Midrange Systems Technical Discussion
Subject: Re: Recommendations for a newcomer?
Would you write an order entry system in SQL?
SQL? Only if filtered result sets are called for. Otherwise, RLA is best for transaction processing.
The question is kind of twisted because you don't write systems in SQL. You use SQL for database I/O. I wouldn't even consider the "L" in SQL to be a language.
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.
midrange.com
