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

× 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.

Subject: How to "omit" a GENERATED ALWAYS column on an Insert that doesn't use VALUES()?
From: Dan <dan27649@xxxxxxxxx>
Date: Thu, 17 Aug 2017 15:01:29 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: How to "omit" a GENERATED ALWAYS column on an Insert that doesn't use VALUES()? , Charles Wilt
Re: How to "omit" a GENERATED ALWAYS column on an Insert that doesn't use VALUES()? , Dan
Re: How to "omit" a GENERATED ALWAYS column on an Insert that doesn't use VALUES()? , Darren Strong
Re: How to "omit" a GENERATED ALWAYS column on an Insert that doesn't use VALUES()? , Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.