Comment 5 for bug 960201

As Ronald Portier pointed, an update to the ir_sequence object breaks the sequence so I think this bug should be medium not low.

If for performance reasons the next number can be updated while generating a sequence number at least it should be read in the edit form so the value won't be corrupted if you save the sequence without making any changes.

Finally, this bug is opened more than 9 months. Amazing.