IrSequence Standard by Default

by ,
v 12.0 Third Party 5
Download for 12.0 series Deploy on Odoo.sh
Technical Name ir_sequence_standard_default
LicenseAGPL-3
Websitehttps://github.com/OCA/server-tools
You bought this module and need support? Click here!

IrSequence Standard by Default

Beta License: AGPL-3 OCA/server-tools Translate me on Weblate Try me on Runbot

Set the implementation to “Standard” in all your current Sequences (ir.sequence) and all new sequences are created as “Standard” by default instead of “No Gap” implementation.

What’s the problem with “No Gap” Sequence Implementations

“No Gap” is the default value of sequences in Odoo. However, this kind of sequences cause more locks and can turn a database slow.

Taking as example an invoice, if you assign an invoice number to one record, but it sill not finish the process, this process must end in order to another invoice could assign a new number and there was no gaps between the invoice numbers. It seems to be good at first sight. But the problem starts when there is a chained process.

Imagine that there is one user that executes a process that produces 100 invoices and these at the same time produces 100 journal entries that also use a consecutive (no gap) sequence. And also those invoices are sent to sign with and external institution (that could take 2 seconds in giving a response because of internet latency or server load), and maybe they made another calculations that makes them to take 5 seconds more for each invoice, and all this is chained to one single transaction. This means that for 8.5 minutes anybody else could confirm invoices, neither journal entries of the involved journals.

Now, think there is 20 users that have to execute a similar process. The problem turns exponential. If another user comes to make an operation with the same jornal it will thrown a concurrency failure.

You can mitigate it if you segment each transaction and don’t chain them. It means, making commit for each invoice or process. It reduces the probability that there is a concurrency error or a lock wait. However, it still not solve it completely.

Why to use Sequences with “Standard” Implementation

If you use the standard sequence of PosgreSQL, it doesn’t lock because at the moment the request is done, the next sequence number it is changed in an isolated transaction, and it have not to wait the other transaction to end. However, if the transaction produces a rollback, this sequence isn’t reverted, it means, it’s lost. It may be not not serious because when you cancel or remove records that number is lost too.

What this module does

To eliminate completely that concurrency/slowness problem, this module changes all the sequences (ir.sequence) implementation from “No Gap” to “Standard” with the awareness that it will skip numbers. In the majority of database models and many users projects there is no problem with that jump occurs.

Table of contents

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Vauxoo

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainers:

moylop260 ebirbe

This module is part of the OCA/server-tools project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.