Another problem is that if for ANY reason the write() method is invoked on the ir_sequence object, the next number and increment on the Postgres sequence are reset to whatever is left in the ir_sequence row.
So let us assume that the starting number was 10. 50 numbers have been issued from the postgres sequence (so next number should be 60). If for any reason ir_sequence number is updated, the next number will be 10 again. -- 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 _______________________________________________ Mailing list: https://launchpad.net/~openerp-india Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-india More help : https://help.launchpad.net/ListHelp
