Is it possible to use the SQL "INSERT using fullselect" form when one of
the columns is defined with "GENERATED ALWAYS AS IDENTITY"? If so, how
does one avoid / omit such a column in the INSERT statement? I'm trying to
avoid having to use the "INSERT using VALUES" form, as this complicates the
dynamic creation of the INSERT statement.
FWIW, I'm on v7r1 and the application is a CLLE which uses the RUNSQL
command to perform the INSERT.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate