Re: Help solve an argument: Reading a SQL index in RPG?

On 2/22/2016 10:07 AM, Rob Michaels wrote:

On Mon, Feb 22, 2016 at 9:00 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

When you write 'converting our database from DDS to SQL' do you mean:
1) Mechanical column by column exact recreation of the DDS using DDL
2) Redesigning the database from the ground up to use normalised tables

We're TRYING to do a mixture of both actually ... we're replicating
the structure of our DDS files using SQL, but at the same time we're
also trying to normalize the data and reduce redundant data with
judicious use of joined views.

What value do you see in a column by column conversion to DDL? The
point being that:

Once the tables are normalised, accessing an individual table via
F-specs is mostly useless. Imagine all the F-specs needed; all the RPG
logic required to programmatically 'join' the various records together
into a coherent unit. As opposed to a simple FETCH from a VIEW which
does all the JOINs for you.

If there's some interim state whereby the table is the exact same layout
whether DDS or DDL, then accessing it via an index/LF still makes sense.

It seems to me that the disagreement will resolve itself once the
database has gone over fully to the new design.