Re: INSERTing datastructure into table with GENERATED ALWAYS column.

Roger,

Check this manual out and search for "extended":

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzajp/rzajppdf.pdf


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (905) 486-1162 x 239
Cell: (416) 317-3144


On 24 January 2017 at 09:29, Robert Rogerson <rrogerson@xxxxxxxxxxx> wrote:

Dave,

I was looking at your suggestion but I couldn't see an example. Then I saw
Brian's suggestion and that seemed to be what I was looking for.

Do you have an example of how I would specify or use an extended indicator
array to limit the columns inserted?

Thanks,

Rob


On 1/24/2017 9:12 AM, dlclark@xxxxxxxxxxxxxxxx wrote:

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 01/24/2017 09:00:12
AM:

So it is better to only put the values that your RPG actually modifies

on

your INSERT statement.

You can still accomplish all that using a single INSERT statement
that lists ALL columns just by using an extended indicator array to
control which columns are actually inserted. Perhaps it is personal
preference but I see this as having greater flexibility with less coding.

Sincerely,

Dave Clark

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD