Re: auto generated ID as primary key

you'll need to write the record in an rpg pgm... not do an insert...

you know, appreciate it, but really looking for others that know what i'm
talking about already without having to try and recreate it... and what
their knowledge and experience is with it.

so thx!

On Thu, Feb 1, 2018 at 9:38 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

This worked fine for me on the same system.

create table rob.jv (
L_ID for column ID
BIGINT not null generated always as
identity (start with 1 increment by 1),
YesICanUseMoreThan4CharactersToDefineAColumn char (10),
CONSTRAINT jvprimarykey PRIMARY KEY (l_id));
insert into rob.jv (YesICanUseMoreThan4CharactersToDefineAColumn)
values('A') with nc;
insert into rob.jv (YesICanUseMoreThan4CharactersToDefineAColumn)
values('B') with nc;
cl: clrsavf rob/rob;
cl: SAVOBJ OBJ(JV) LIB(ROB) DEV(*SAVF) OBJTYPE(*FILE) SAVF(ROB/ROB);
cl: crtlib rob2;
cl: RSTOBJ OBJ(JV) SAVLIB(ROB) DEV(*SAVF) OBJTYPE(*FILE) SAVF(ROB/ROB)
RSTLIB(ROB2);
insert into rob2.jv (YesICanUseMoreThan4CharactersToDefineAColumn)
values('C') with nc;
select * from rob2.jv for fetch only;
This returned 1-3 for L_ID.

So I saved it again and restored it to another system.
I inserted another row
Did another select
This returned 1-4 for L_ID.

IBM i 7.3 with PTF groups updated as of mid December.

Please show one of your inserts. I'm curious if you're assigning a value
for L_ID or something.

Keep in mind that the last used is not stored in some external table. It's
in the object header information itself.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/01/2018 09:30 AM
Subject: Re: auto generated ID as primary key
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



sure, save/restore...


On Thu, Feb 1, 2018 at 9:16 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

IDK where you get the idea that it's bad practice to have keys defined

in

tables like that. Perhaps that was true back on the S/3 but it hasn't
been true for a long time now.

What is your definition of rehome? Save/restore to a different library,
system, ?




Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 02/01/2018 08:44 AM
Subject: auto generated ID as primary key
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



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


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

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


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