We had a case just this week in which we first used SETLL ... READE... DELETE loops to remove records from "work" tables. Then switched to DELETE FROM XYZ WHERE ...
There was a dramatic performance improvement in the latter.
This was part of a job stream to build school class schedules & enroll students based on student course requests and available school resources (teachers, days, periods, class rooms, etc.) where tens of thousands of temporary records may be generated and deleted over iterations.
Use SQL for set based operations.
________________________________
From: Dave <dfx1@xxxxxxxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, September 7, 2011 1:13 PM
Subject: advantages of using embedded sql
Hi all, I need to list some advantages of using embedded sql in rpg
programmes over using ordinary rpg code. We don't actually use DDL, so I'm
assuming that there are far less advantages in our case. Right or wrong?
Thank you very much!!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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
