openerp-india team mailing list archive

[Manu <960201@xxxxxxxxxxxxxxxxxx>]

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.

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/960201

Title:
  [6.1] Sequence number_next gives invalid feedback since new
  implementation

Status in OpenERP Server:
  Confirmed

Bug description:
  A "new" sequence implementation named "standard" is using the pgsql built-in sequence.
  The "Next Number" value is incorrect because not updated when the built-in one is ('ir_sequence_%03d').

  To reproduce:

  [PURCHASES] -> [Purchase Management] -> [Purchase Orders] -> [Create]: PO00001
  [PURCHASES] -> [Purchase Management] -> [Purchase Orders] -> [Create]: PO00002
  [PURCHASES] -> [Purchase Management] -> [Purchase Orders] -> [Create]: PO00003
  [PURCHASES] -> [Purchase Management] -> [Purchase Orders] -> [Create]: PO00004

  [SETTINGS] -> [Configuration] -> [Sequences & Identifiers] ->
  [Sequences]: Purchase Order with Next Number = 1 (should be 5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/960201/+subscriptions