Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Enhancement Requests and Suggestions » View Thread |
Messages 1 to 3 of 3 total |
Copy on append |
Tue, Sep 12 2017 8:19 AM | Permanent Link |
Roy Lambert NLH Associates 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 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. 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. Tim Young Elevate Software www.elevatesoft.com |
Wed, Sep 13 2017 2:42 AM | Permanent Link |
Roy Lambert NLH Associates 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 |
This web page was last updated on Thursday, March 28, 2024 at 06:05 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |