Re: auto generated ID as primary key

[Jay Vaughn <jeffersonvaughn@xxxxxxxxx>]

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