Re: SQL is amazing was ( Avoid Level checks )

Or, even better, put those SQL scripts in a real DB2 table instead of using
separate text files or source members. That way, you can easily run SQL
queries to find your desired scripts (ex: search for a specific table or
column name), or even easily run SQL UPDATE statements to change the
scripts in bulk.

Run them using a central custom SQL script processor, which
allows centralized error handling, error logging, and performance logging.
It also facilitates the ability to extend SQL's capabilities to things like
conditional execution of SQL statements within a script.

Mike

On Wed, Jun 29, 2022 at 2:46 AM Brian Parkins <goodprophet.bp@xxxxxxxxx>
wrote:

Frank, interesting that you used embedded SQL.

Was there a reason that SQL scripts (text files) were not acceptable?
(These could then be used through an number of SQL processors such as
RUNSQLSTM or the ACS Run SQL Scripts interface.) Even a CL program
containing RUNSQL statements seems less involved than writing SQLRPGLE
programs for "housekeeping".

Just curious. (Applaud the approach!)

Brian.

On 29/06/2022 01:14, Frank Kolmann wrote:

I demanded my team that all and any SQL CREATE must be implemented as
embedded SQL in a SQLRPGLE.
One program per file that was created via SQL of course there could be
a CREATE and many CREATE INDEX per table as well as DROP for recreation..
It was tricky finding files that were created interactively, but we
had a SOX audit procedure that mostly worked ok.
This was for documentation purposes and for recreate, and the SOX
auditors were happy.
So now I had documentation as good as DDS. Btw did you ever verify the
DDS source matched the actual file? Our auditors did spot checks.
There are many ways to skin that cat.

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com