|
Alan Campin
Every AS/400 shop. Absolute agony about making a change to a table.
You might gain more traction if you were not so predisposed to absolutes
and hyperbole. In the SQL vs. RLA debate there are no real absolutes either
way. Both have appropriate use cases. You're raising artificial barriers
against RLA by ridiculing it and urging all DB I/O to be handled by SQL
alone.
We use both SQL and RLA and don't agonize over changing table layouts.
We're pretty agile with respect to changes to table layouts. We use a
utility to scan RPG source members that would be affected by table layouts,
and optionally compile them automatically. There typically aren't a lot. We
encapsulate DB I/O appropriately. We use SQL in modules that generate
filtered lists and reports, so none of those source members are affected.
We don't recompile "the world".
-Nathan
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
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.