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

Yes. I wouldn't rely on multiple ALTER tables. A hidden field can be
referenced explicitly, so maybe you could add it to the programs that need
it. It can be added after the '*' as an additional field.



___________________________________
Darren Strong
Dekko





From: Dan <dan27649@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/17/2017 03:30 PM
Subject: Re: How to "omit" a GENERATED ALWAYS column on an Insert
that doesn't use VALUES()?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I thought about this before and, yes, there are other SELECT * queries on
these tables. But I wondered about using ALTER to change this on the fly:
Alter table xyz Alter column IQXSEQUENC SET implicitly hidden
Insert using fullselect
Alter table xyz Alter column IQXSEQUENC SET not hidden

This actually works, but the ALTER needs an *EXCL lock (makes sense).
While, normally, this would not be a problem, I don't want to chance that
someone else is querying the file when my application attempts to do the
ALTERs, causing SQL0913.

- Dan

On Thu, Aug 17, 2017 at 3:12 PM, Darren Strong <darren@xxxxxxxxx> wrote:

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.