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



"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 12/12/2018
02:31:45 PM:
i have a statement

insert into ldatat3x.ftpdtl
(select *
from ldatad3x.ftpdtl
where dftpid = 'PMIISGN-G')

source and target file are same of course except in different libs...
primary key on both is ID which is auto generated.

to avoid, Value cannot be specified for GENERATED ALWAYS column DID., i
know I can layout the source/target columns, but what a PIA.
is there an easy way to simply ignore/override the ID column and have
sql,
be smart enough to assign a new one from the target table/rows?

I've tried the following with no luck...

insert into ldatat3x.ftpdtl overriding system value
(select *
from ldatad3x.ftpdtl
where dftpid = 'PMIISGN-G')


That is example what IBM says. So, what do you mean by "no luck"?

<quote>
You can force the system to use the value from the select for a GENERATED
ALWAYS identity column by specifying OVERRIDING SYSTEM VALUE. For example,
issue the following statement:

INSERT INTO ORDERS OVERRIDING SYSTEM VALUE
(SELECT * FROM TODAYS_ORDER)

This INSERT statement uses the value from SELECT; it does not generate a
new value for the identity column. You cannot provide a value for an
identity column created using GENERATED ALWAYS without using the
OVERRIDING SYSTEM VALUE clause.
</quote>


Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.