Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 3 of 3 total
Thread Copy on append
Tue, Sep 12 2017 8:19 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Currently copy on append copies all columns, and then give a fault when its saved if, as in my case column 1 is

"_ID" INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 0, INCREMENT BY 1) NOT NULL,

I don't know if it would break anyone's existing code but I'd like to see those type of columns set to NULL rather than the value.

Roy Lambert
Tue, Sep 12 2017 1:10 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< I don't know if it would break anyone's existing code but I'd like to see those type of columns set to NULL rather than the value. >>

The issue is the BY DEFAULT as opposed to ALWAYS.  It's hard to glean the intent of the developer from just those signals, so copy on append would have to be supplemented with another property to control what to do in such cases.

Added to the list. Smile

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Sep 13 2017 2:42 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim

><< I don't know if it would break anyone's existing code but I'd like to see those type of columns set to NULL rather than the value. >>
>
>The issue is the BY DEFAULT as opposed to ALWAYS. It's hard to glean the intent of the developer from just those signals, so copy on append would have to be supplemented with another property to control what to do in such cases.

How about just null it IF its the primary key or part thereof?

Roy
Image