I claimed SQL is better for transaction processing. Then you gave me an example that is not transaction processing; it was really old, really archaic batch processing.
No. I would not write an order entry system in SQL. I would write it in a combination of HTML, XML, javascript, java, jsp, and JDBC. JDBC includes SQL transaction processing.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Tuesday, May 14, 2013 3:42 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Recommendations for a newcomer?
Yeah, I know, but Dan claimed SQL is better.
:-))
Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx
-----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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
