B
Ben Wildie
Guest
encountering an odd issue with a sequence in Openedge version 11.7. While testing to ensure that using a sequence to generate a key value for a high usage table would not get duplicate values when setting the key using NEXT-VALUE.
To test this I ran code in a loop in 2 separate instances connected to the same db to ensure no duplicates would occur. The results are:
Does anyone have any idea why this could be happening? And if this could happen on a server running an Openedge built program as opposed to 2 people running code in scratchpad.
Continue reading...
To test this I ran code in a loop in 2 separate instances connected to the same db to ensure no duplicates would occur. The results are:
- run both instances on one PC: no issue sequence numbers just interlace as program 1 and 2 each grab the next number
- Run instances on separate PCs (same DB): dupliccate sequence numbers are generated, but anytime a duplicate happens the next number is 2 higher than the last (eg both output 2 and the next number is 4) so it is clearly incrementing correctly.
Does anyone have any idea why this could be happening? And if this could happen on a server running an Openedge built program as opposed to 2 people running code in scratchpad.
Continue reading...