Re: How to "omit" a GENERATED ALWAYS column on an Insert that doesn't use VALUES()?

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 08/17/2017
03:46:41 PM:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 08/17/2017
03:13:13 PM:

Best practice is not to use SELECT *, always use an explicit column

list.

This applies to INSERT too...

Don't do

INSERT INTO mytable
SELECT <...>

Instead, use

INSERT INTO mytable (col1, col2, col3, <...>)
SELECT <...>

In principle, I agree with you (always use an explicit column
list). But, I wonder, isn't there a third choice?

INSERT INTO mytable
SELECT col1, col2, col3, ... FROM ...etc...

I just realized that perhaps the problem for the OP is having to
create any column list at all. If so, then I think there is no other way
to circumvent the GENERATED ALWAYS column in the target table. If RPG it
can be circumvented using an extended indicator array to IGNORE that
column. But apparently that is also not exactly what the OP wants.

Sincerely,

Dave Clark