I agree 100% with Aaron, here. IMO, it's best to come up with the best
solution (flexible, speed).
And if that means combining the 2 (SQL for reading, and RLA for updating),
why not. We've
been doing that for sometime now. And the flexibilty we put into our
programs is awesome.
Don't limit your code to just one way.
David
David L. Mosley, Jr.
Technical Solutions Architect
Dancik International, Ltd.
2000 CentreGreen Way, Suite 250
Cary, NC 27513
www.dancik.com
Aaron Bartell <aaronbartell@xxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
11/19/2010 10:33 AM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
To
"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
cc
Subject
Re: RPG SQL and Cursors
And why not? Say you had an app with a list of records that the user was
allowed to sort by any column and specify search criteria in a text input
at
the top - that is much easier to code in SQL than RLA in my opinion, but
then when it comes time to edit one of the result records and update it,
well then I go back to RLA.
Aaron Bartell
www.MowYourLawn.com/blog
www.OpenRPGUI.com
www.SoftwareSavesLives.com
On Fri, Nov 19, 2010 at 9:13 AM, <dieter.bender@xxxxxxxxxxxx> wrote:
... I wouldn't use a mix of RLA and SQL, but maybe thats a question of
flavour and I'm tired of discussions about microseconds.
Dieter
midrange.com
