You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

455 lines
14 KiB

[ADD] ir_sequence_standard_default: Use Standard instead No Gap sequence 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 Sequences with "No Gap" Implementation?** "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 start when there is and 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. Also, all newly created sequences will be by default in "Standard" implementation.
5 years ago
  1. <?xml version="1.0" encoding="utf-8" ?>
  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  3. <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  4. <head>
  5. <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  6. <meta name="generator" content="Docutils 0.15.1: http://docutils.sourceforge.net/" />
  7. <title>IrSequence Standard by Default</title>
  8. <style type="text/css">
  9. /*
  10. :Author: David Goodger (goodger@python.org)
  11. :Id: $Id: html4css1.css 7952 2016-07-26 18:15:59Z milde $
  12. :Copyright: This stylesheet has been placed in the public domain.
  13. Default cascading style sheet for the HTML output of Docutils.
  14. See http://docutils.sf.net/docs/howto/html-stylesheets.html for how to
  15. customize this style sheet.
  16. */
  17. /* used to remove borders from tables and images */
  18. .borderless, table.borderless td, table.borderless th {
  19. border: 0 }
  20. table.borderless td, table.borderless th {
  21. /* Override padding for "table.docutils td" with "! important".
  22. The right padding separates the table cells. */
  23. padding: 0 0.5em 0 0 ! important }
  24. .first {
  25. /* Override more specific margin styles with "! important". */
  26. margin-top: 0 ! important }
  27. .last, .with-subtitle {
  28. margin-bottom: 0 ! important }
  29. .hidden {
  30. display: none }
  31. .subscript {
  32. vertical-align: sub;
  33. font-size: smaller }
  34. .superscript {
  35. vertical-align: super;
  36. font-size: smaller }
  37. a.toc-backref {
  38. text-decoration: none ;
  39. color: black }
  40. blockquote.epigraph {
  41. margin: 2em 5em ; }
  42. dl.docutils dd {
  43. margin-bottom: 0.5em }
  44. object[type="image/svg+xml"], object[type="application/x-shockwave-flash"] {
  45. overflow: hidden;
  46. }
  47. /* Uncomment (and remove this text!) to get bold-faced definition list terms
  48. dl.docutils dt {
  49. font-weight: bold }
  50. */
  51. div.abstract {
  52. margin: 2em 5em }
  53. div.abstract p.topic-title {
  54. font-weight: bold ;
  55. text-align: center }
  56. div.admonition, div.attention, div.caution, div.danger, div.error,
  57. div.hint, div.important, div.note, div.tip, div.warning {
  58. margin: 2em ;
  59. border: medium outset ;
  60. padding: 1em }
  61. div.admonition p.admonition-title, div.hint p.admonition-title,
  62. div.important p.admonition-title, div.note p.admonition-title,
  63. div.tip p.admonition-title {
  64. font-weight: bold ;
  65. font-family: sans-serif }
  66. div.attention p.admonition-title, div.caution p.admonition-title,
  67. div.danger p.admonition-title, div.error p.admonition-title,
  68. div.warning p.admonition-title, .code .error {
  69. color: red ;
  70. font-weight: bold ;
  71. font-family: sans-serif }
  72. /* Uncomment (and remove this text!) to get reduced vertical space in
  73. compound paragraphs.
  74. div.compound .compound-first, div.compound .compound-middle {
  75. margin-bottom: 0.5em }
  76. div.compound .compound-last, div.compound .compound-middle {
  77. margin-top: 0.5em }
  78. */
  79. div.dedication {
  80. margin: 2em 5em ;
  81. text-align: center ;
  82. font-style: italic }
  83. div.dedication p.topic-title {
  84. font-weight: bold ;
  85. font-style: normal }
  86. div.figure {
  87. margin-left: 2em ;
  88. margin-right: 2em }
  89. div.footer, div.header {
  90. clear: both;
  91. font-size: smaller }
  92. div.line-block {
  93. display: block ;
  94. margin-top: 1em ;
  95. margin-bottom: 1em }
  96. div.line-block div.line-block {
  97. margin-top: 0 ;
  98. margin-bottom: 0 ;
  99. margin-left: 1.5em }
  100. div.sidebar {
  101. margin: 0 0 0.5em 1em ;
  102. border: medium outset ;
  103. padding: 1em ;
  104. background-color: #ffffee ;
  105. width: 40% ;
  106. float: right ;
  107. clear: right }
  108. div.sidebar p.rubric {
  109. font-family: sans-serif ;
  110. font-size: medium }
  111. div.system-messages {
  112. margin: 5em }
  113. div.system-messages h1 {
  114. color: red }
  115. div.system-message {
  116. border: medium outset ;
  117. padding: 1em }
  118. div.system-message p.system-message-title {
  119. color: red ;
  120. font-weight: bold }
  121. div.topic {
  122. margin: 2em }
  123. h1.section-subtitle, h2.section-subtitle, h3.section-subtitle,
  124. h4.section-subtitle, h5.section-subtitle, h6.section-subtitle {
  125. margin-top: 0.4em }
  126. h1.title {
  127. text-align: center }
  128. h2.subtitle {
  129. text-align: center }
  130. hr.docutils {
  131. width: 75% }
  132. img.align-left, .figure.align-left, object.align-left, table.align-left {
  133. clear: left ;
  134. float: left ;
  135. margin-right: 1em }
  136. img.align-right, .figure.align-right, object.align-right, table.align-right {
  137. clear: right ;
  138. float: right ;
  139. margin-left: 1em }
  140. img.align-center, .figure.align-center, object.align-center {
  141. display: block;
  142. margin-left: auto;
  143. margin-right: auto;
  144. }
  145. table.align-center {
  146. margin-left: auto;
  147. margin-right: auto;
  148. }
  149. .align-left {
  150. text-align: left }
  151. .align-center {
  152. clear: both ;
  153. text-align: center }
  154. .align-right {
  155. text-align: right }
  156. /* reset inner alignment in figures */
  157. div.align-right {
  158. text-align: inherit }
  159. /* div.align-center * { */
  160. /* text-align: left } */
  161. .align-top {
  162. vertical-align: top }
  163. .align-middle {
  164. vertical-align: middle }
  165. .align-bottom {
  166. vertical-align: bottom }
  167. ol.simple, ul.simple {
  168. margin-bottom: 1em }
  169. ol.arabic {
  170. list-style: decimal }
  171. ol.loweralpha {
  172. list-style: lower-alpha }
  173. ol.upperalpha {
  174. list-style: upper-alpha }
  175. ol.lowerroman {
  176. list-style: lower-roman }
  177. ol.upperroman {
  178. list-style: upper-roman }
  179. p.attribution {
  180. text-align: right ;
  181. margin-left: 50% }
  182. p.caption {
  183. font-style: italic }
  184. p.credits {
  185. font-style: italic ;
  186. font-size: smaller }
  187. p.label {
  188. white-space: nowrap }
  189. p.rubric {
  190. font-weight: bold ;
  191. font-size: larger ;
  192. color: maroon ;
  193. text-align: center }
  194. p.sidebar-title {
  195. font-family: sans-serif ;
  196. font-weight: bold ;
  197. font-size: larger }
  198. p.sidebar-subtitle {
  199. font-family: sans-serif ;
  200. font-weight: bold }
  201. p.topic-title {
  202. font-weight: bold }
  203. pre.address {
  204. margin-bottom: 0 ;
  205. margin-top: 0 ;
  206. font: inherit }
  207. pre.literal-block, pre.doctest-block, pre.math, pre.code {
  208. margin-left: 2em ;
  209. margin-right: 2em }
  210. pre.code .ln { color: grey; } /* line numbers */
  211. pre.code, code { background-color: #eeeeee }
  212. pre.code .comment, code .comment { color: #5C6576 }
  213. pre.code .keyword, code .keyword { color: #3B0D06; font-weight: bold }
  214. pre.code .literal.string, code .literal.string { color: #0C5404 }
  215. pre.code .name.builtin, code .name.builtin { color: #352B84 }
  216. pre.code .deleted, code .deleted { background-color: #DEB0A1}
  217. pre.code .inserted, code .inserted { background-color: #A3D289}
  218. span.classifier {
  219. font-family: sans-serif ;
  220. font-style: oblique }
  221. span.classifier-delimiter {
  222. font-family: sans-serif ;
  223. font-weight: bold }
  224. span.interpreted {
  225. font-family: sans-serif }
  226. span.option {
  227. white-space: nowrap }
  228. span.pre {
  229. white-space: pre }
  230. span.problematic {
  231. color: red }
  232. span.section-subtitle {
  233. /* font-size relative to parent (h1..h6 element) */
  234. font-size: 80% }
  235. table.citation {
  236. border-left: solid 1px gray;
  237. margin-left: 1px }
  238. table.docinfo {
  239. margin: 2em 4em }
  240. table.docutils {
  241. margin-top: 0.5em ;
  242. margin-bottom: 0.5em }
  243. table.footnote {
  244. border-left: solid 1px black;
  245. margin-left: 1px }
  246. table.docutils td, table.docutils th,
  247. table.docinfo td, table.docinfo th {
  248. padding-left: 0.5em ;
  249. padding-right: 0.5em ;
  250. vertical-align: top }
  251. table.docutils th.field-name, table.docinfo th.docinfo-name {
  252. font-weight: bold ;
  253. text-align: left ;
  254. white-space: nowrap ;
  255. padding-left: 0 }
  256. /* "booktabs" style (no vertical lines) */
  257. table.docutils.booktabs {
  258. border: 0px;
  259. border-top: 2px solid;
  260. border-bottom: 2px solid;
  261. border-collapse: collapse;
  262. }
  263. table.docutils.booktabs * {
  264. border: 0px;
  265. }
  266. table.docutils.booktabs th {
  267. border-bottom: thin solid;
  268. text-align: left;
  269. }
  270. h1 tt.docutils, h2 tt.docutils, h3 tt.docutils,
  271. h4 tt.docutils, h5 tt.docutils, h6 tt.docutils {
  272. font-size: 100% }
  273. ul.auto-toc {
  274. list-style-type: none }
  275. </style>
  276. </head>
  277. <body>
  278. <div class="document" id="irsequence-standard-by-default">
  279. <h1 class="title">IrSequence Standard by Default</h1>
  280. <!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  281. !! This file is generated by oca-gen-addon-readme !!
  282. !! changes will be overwritten. !!
  283. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
  284. <p><a class="reference external" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a> <a class="reference external" href="https://github.com/OCA/server-tools/tree/12.0/ir_sequence_standard_default"><img alt="OCA/server-tools" src="https://img.shields.io/badge/github-OCA%2Fserver--tools-lightgray.png?logo=github" /></a> <a class="reference external" href="https://translation.odoo-community.org/projects/server-tools-12-0/server-tools-12-0-ir_sequence_standard_default"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external" href="https://runbot.odoo-community.org/runbot/149/12.0"><img alt="Try me on Runbot" src="https://img.shields.io/badge/runbot-Try%20me-875A7B.png" /></a></p>
  285. <p>Set the implementation to “Standard” in all your current Sequences
  286. (ir.sequence) and all new sequences are created as “Standard” by default
  287. instead of “No Gap” implementation.</p>
  288. <div class="section" id="what-s-the-problem-with-no-gap-sequence-implementations">
  289. <h1>What’s the problem with “No Gap” Sequence Implementations</h1>
  290. <p>“No Gap” is the default value of sequences in Odoo. However, this kind of
  291. sequences cause more locks and can turn a database slow.</p>
  292. <p>Taking as example an invoice, if you assign an invoice number to one record,
  293. but it sill not finish the process, this process must end in order to another
  294. invoice could assign a new number and there was no gaps between the invoice
  295. numbers. It seems to be good at first sight. But the problem starts when there
  296. is a chained process.</p>
  297. <p>Imagine that there is one user that executes a process that produces 100
  298. invoices and these at the same time produces 100 journal entries that also use
  299. a consecutive (no gap) sequence. And also those invoices are sent to sign with
  300. and external institution (that could take 2 seconds in giving a response
  301. because of internet latency or server load), and maybe they made another
  302. calculations that makes them to take 5 seconds more for each invoice, and all
  303. this is chained to one single transaction. This means that for 8.5 minutes
  304. anybody else could confirm invoices, neither journal entries of the involved
  305. journals.</p>
  306. <p>Now, think there is 20 users that have to execute a similar process. The
  307. problem turns exponential. If another user comes to make an operation with the
  308. same jornal it will thrown a concurrency failure.</p>
  309. <p>You can mitigate it if you segment each transaction and don’t chain them. It
  310. means, making commit for each invoice or process. It reduces the
  311. probability that there is a concurrency error or a lock wait. However, it still
  312. not solve it completely.</p>
  313. </div>
  314. <div class="section" id="why-to-use-sequences-with-standard-implementation">
  315. <h1>Why to use Sequences with “Standard” Implementation</h1>
  316. <p>If you use the standard sequence of PosgreSQL, it doesn’t lock because at the
  317. moment the request is done, the next sequence number it is changed in an
  318. isolated transaction, and it have not to wait the other transaction to end.
  319. However, if the transaction produces a rollback, this sequence isn’t reverted,
  320. it means, it’s lost. It may be not not serious because when you cancel or
  321. remove records that number is lost too.</p>
  322. </div>
  323. <div class="section" id="what-this-module-does">
  324. <h1>What this module does</h1>
  325. <p>To eliminate completely that concurrency/slowness problem, this module changes
  326. all the sequences (ir.sequence) implementation from “No Gap” to “Standard” with
  327. the awareness that it will skip numbers. In the majority of database models
  328. and many users projects there is no problem with that jump occurs.</p>
  329. <p><strong>Table of contents</strong></p>
  330. </div>
  331. <div class="section" id="bug-tracker">
  332. <h1>Bug Tracker</h1>
  333. <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/server-tools/issues">GitHub Issues</a>.
  334. In case of trouble, please check there if your issue has already been reported.
  335. If you spotted it first, help us smashing it by providing a detailed and welcomed
  336. <a class="reference external" href="https://github.com/OCA/server-tools/issues/new?body=module:%20ir_sequence_standard_default%0Aversion:%2012.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p>
  337. <p>Do not contact contributors directly about support or help with technical issues.</p>
  338. </div>
  339. <div class="section" id="credits">
  340. <h1>Credits</h1>
  341. <div class="section" id="authors">
  342. <h2>Authors</h2>
  343. <ul class="simple">
  344. <li>Vauxoo</li>
  345. </ul>
  346. </div>
  347. <div class="section" id="contributors">
  348. <h2>Contributors</h2>
  349. <ul class="simple">
  350. <li>Moises López &lt;<a class="reference external" href="mailto:moylop260&#64;vauxoo.com">moylop260&#64;vauxoo.com</a>&gt;</li>
  351. <li>Erick Birbe &lt;<a class="reference external" href="mailto:erick&#64;vauxoo.com">erick&#64;vauxoo.com</a>&gt;</li>
  352. </ul>
  353. </div>
  354. <div class="section" id="maintainers">
  355. <h2>Maintainers</h2>
  356. <p>This module is maintained by the OCA.</p>
  357. <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
  358. <p>OCA, or the Odoo Community Association, is a nonprofit organization whose
  359. mission is to support the collaborative development of Odoo features and
  360. promote its widespread use.</p>
  361. <p>Current <a class="reference external" href="https://odoo-community.org/page/maintainer-role">maintainers</a>:</p>
  362. <p><a class="reference external" href="https://github.com/moylop260"><img alt="moylop260" src="https://github.com/moylop260.png?size=40px" /></a> <a class="reference external" href="https://github.com/ebirbe"><img alt="ebirbe" src="https://github.com/ebirbe.png?size=40px" /></a></p>
  363. <p>This module is part of the <a class="reference external" href="https://github.com/OCA/server-tools/tree/12.0/ir_sequence_standard_default">OCA/server-tools</a> project on GitHub.</p>
  364. <p>You are welcome to contribute. To learn how please visit <a class="reference external" href="https://odoo-community.org/page/Contribute">https://odoo-community.org/page/Contribute</a>.</p>
  365. </div>
  366. </div>
  367. </div>
  368. </body>
  369. </html>