Re: [dev] IStorage.lastOID() proposal (was Re: [dev] RFC IMVCCStorage everywhere (Move ZODB's MVCC to storage layer))
Vincent Pelletier <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Organization | Nexedi |
| Message-ID | <20160620044333.01355d8a@vincent-tkpad> |
On Fri, 17 Jun 2016 07:47:22 -0400, Jim Fulton <[email protected]> wrote : > This is an interesting approach. I doubt that you can have truly > failure free transactions. Network or servers can fail. Presumably > the probability of failure is very low. I doubt the risk of a random > oid collision would increase the chance of failure significantly. Even > if you had several billion objects in your database, the chance of a > collision would less than one in a billion (assuming you're adding a > single object). IIRC, Julien needed to be sure the action was not replied, with the drawback that it may fail on its one execution. Then there was some out-of-zope-transaction-manager ways to later (hours, ...) detect if nothing happened, and trigger another single call. -- Vincent Pelletier ERP5 - open source ERP/CRM for flexible enterprises -- You received this message because you are subscribed to the Google Groups "zodb" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
smime.p7s
(application/pkcs7-signature, 3.2 KB) - not displayed