Re: SQL is amazing was ( Avoid Level checks )

[Frank Kolmann <Frank.Kolmann@xxxxxxxxx>]

Hi Brian

I did that because then it was simple to record the code in Implementer 
Source Control system.

Frank

On 29/06/2022 7:45 pm, Brian Parkins 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.