×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
One possible solution is to define the column as IMPLICITLY HIDDEN, but I
don't know if you have the ability to change the column definition at this
point, or if it would cause problems where programs are expecting to see
this field if they select * from the file.
http://ibmsystemsmag.com/blogs/db2utor/archive/implicitly-hidden-columns/
From: Dan <dan27649@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/17/2017 03:01 PM
Subject: How to "omit" a GENERATED ALWAYS column on an Insert that
doesn't use VALUES()?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
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.
- Dan
midrange.com
