Re: embedded SQL - how to insert with a GENERATED ALWAYS AS IDENTITY column

Actually that variation on the SQL INSERT is not a valid option for a GENERATED ALWAYS IDENTITY column, at least not with the OVERRIDING USER VALUE clause, but with an override, the identity value would not be generated, and that is not likely the desired effect. The literal zero versus the word DEFAULT asks\attempts to insert the numeric value zero as the identity value for column TKTTKTDID, which would require an override to the GENERATED value. The statement with the numeric literal would fail with SQL0798 "Value cannot be specified for GENERATED ALWAYS column TKTTKTDID."

Regards, Chuck

On 2/15/11 10:32 AM, Christen, Duane wrote:

You can also do:

Exec SQL
Insert into pdatalib/TKT001DPF overriding user value
Values(:P1_SysID , :P2_AEmail , :P3_REmail,
:P4_TEmail , :P5_PrbName , :P6_Priority,
:P7_Status , :P8_TktType, :P9_Subject,
:PA_Body , :TICKET# , :TIMSTAMP,
0);

Although I will look into DEFAULT, as Birgitta suggested.

Birgitta Hauser on Tuesday, February 15, 2011 12:05 AM wrote:

Try:

Exec SQL
Insert into pdatalib/TKT001DPF VALUES
( :P1_SysID , :P2_AEmail , :P3_REmail,
:P4_TEmail , :P5_PrbName , :P6_Priority,
:P7_Status , :P8_TktType, :P9_Subject,
:PA_Body , :TICKET# , :TIMSTAMP,
DEFAULT) ;

<<SNIP>>