Re: auto generated ID as primary key

Save / restore or CPYF?

AFAIK, save / restore should work...

CPYF doesn't (or at least didn't used to) work with GENERATED AS IDENTITY
columns...

You have to manually issue a
ALTER TABLE ALTER COLUMN L_ID RESTART WITH xxxx

Prior to using the table with either SQL or RPG.

I built a program that would do so I used as an exit program with our CMS...

Charles

On Thu, Feb 1, 2018 at 6:38 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

though i know this is bad practice (to have keys defined in tables), my
current employer currently has tables with...

L_ID for column ID
BIGINT not null generated always as
identity (start with 1 increment by 1),

Now when this file is "re-homed" it knocks the auto generate row id out of
whack and creates a duplicate record error when a pgm tries to write to
it. And of course we have to manually reset the row id.

My guess is because of the (start with 1 increment by 1) - meaning, once it
is re-homed it somehow thinks it needs to start at 1 again.

Is that true? Ideally i'd like to remove the ID from being a primary key
on the table, but would at least removing (start with 1 increment by 1)
resolve the re-homing and duplicate record issue, or no? How exactly does
this work?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD