[MERGE] ir_sequence standard and no_gap implementation by Thu (vmt)
authorAntony Lesuisse <al@openerp.com>
Fri, 30 Sep 2011 19:00:53 +0000 (21:00 +0200)
committerAntony Lesuisse <al@openerp.com>
Fri, 30 Sep 2011 19:00:53 +0000 (21:00 +0200)
commitff1ca3c4fbaabe47f22976c3fbf03befdef891a0
tree27e1c134f4cf942f548d8e141420203e89067db5
parent859cf8ed3cf702c247daeda2bdf930db0dec0004
parent997d9f41782cba16eb50abf18b08d877e020414d
[MERGE] ir_sequence standard and no_gap implementation by Thu (vmt)
standard uses postgresql sequences, no locks, gaps are allowed.
no_gap uses an SELECT FOR UPDATE NO WAIT, no gaps are allowed but an exception could be raised if the lock is unavailable.
we also deprecated the infamous get()/get_id() api in favor of next_by_code()/next_by_id()
the specs of this change were inspired by openlabs sequence-postgres module

bzr revid: al@openerp.com-20110930190053-ovd4qlwt7hll02ch