Re: update column with a sequential #

[CRPence <CRPbottle@xxxxxxxxx>]

  Ignoring "the same between files"...

  Depending on the definition of /unique/ employed, the column may be 
able to be set to the NULL value for every row, thus freeing all 
non-null values from any effect of /duplicate/ value.  Or the /unique/ 
attribute could be removed temporarily to allow duplicates while work is 
performed without isolation.

  Or, given a small enough set with journaling in effect, the following 
should suffice, to allow apparent duplicates pending a commit:

    create sequence myseq as integer start with 1 increment by 1 no 
cache order
    ;
    update the_table set seq# = next value for myseq with UR
    ;
    commit
    ;
    drop sequence myseq
    ;

Regards, Chuck

On 30 Apr 2013 15:13, Stone, Joel wrote:
> No significance to number.
>
> Just doing a regression test between a file updated with the current
> prod version of a pgm and a modified version of same pgm.
>
> Need to force the seq# field to 1,2,3,4, etc so it is the same
> between files, and it is a unique key so I can't simply clear it
> out.
>
> Roger Harman on Tuesday, April 30, 2013 5:10 PM  wrote:
>
> > Any significance to the number?
> >
> > I had to do something similar a long time ago. RGZPFM to get rid of
> > deleted records and then just used the RRN as the value for my
> > update.
> >
> > How do you plan to maintain it going forward?
> >
> > Stone, Joel on Tuesday, April 30, 2013 3:01 PM wrote:
> >
> > > Is it possible to update a column with a sequential # ?
> > >
> > > So that for this particular column, each row has a value 1 higher
> > > than the prior row?
> > >
> > > Something like
> > >
> > > UPDATE filename set SEQCOL to prior SEQCOL + 1
> > >
> > > (This is a DDS created file that does NOT have an identity column.)