openerp-india team mailing list archive

[Yann Papouin <yann.papouin@xxxxxxxxx>]

Public bug reported:

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)

** Affects: openobject-server
     Importance: Undecided
         Status: New

-- 
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:
  New

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