- Shipped
- 8 Novemba 2026, 08:35 UTC
- Author
- Kamo
- Commit
- d100d86
Kazi ili idadi walikuwa hesabu (kazi) + 1, hivyo kazi mbili kuongezeka kwa mara moja inaweza kushiriki moja, na kazi kuongezeka kutoka kwa ajili ya kulipwa (ServiceFulfillmentPolicy) akawa na idadi yoyote wakati wote. ServiceJobNumbers sasa mints WO-00001… chini ya kufuli PESSIMISTIC_WRITE juu ya org ya commerce_document_counter safu (DocumentType.SERVICE_JOB, mfululizo mwaka 0 — mbio mfululizo), mbegu mara moja kutoka juu WO- idadi ya org tayari ina. Wote kujenga njia kutumia; createJob ni @RetryOnDbConflict kwa Yugabyte ya 40001 juu ya alidai counter. ux_service_job_org_number (org_id, job_number) ni backstop, kutumika na mkono NONCONCURRENTLY baada ya idadi null walikuwa backfilled. kazi tena huenda kwa Invoiced na hali ya mabadiliko: Invoiced maana ankara ipo, na tu kujenga moja (InvoicingService) anaweka kazi huko. CommerceInvoicePayment (commerce_invoice_payments, kutumika kwa mkono) rekodi kila malipo dhidi ya CommerceInvoice, hivyo yake AMOUNT_PAID / PAID / PARTIALLY_PAID nguzo hatimaye kuwa na mwandishi. CommerceInvoiceRepository faida safu-kufungwa kusoma na kwa-mteja finder; ServiceJobRepository faida claimForInvoicing.