3 ms·
A cursory glance through the code revealed a bug: https://bitbucket.org/codernity/codernitydb/issue/1/_rev-not-guaranteed-to-be-unique https://bitbucket.org/cod
by mmcnickle 14y ago
A cursory glance through the code revealed a bug: https://bitbucket.org/codernity/codernitydb/issue/1/_rev-not-guaranteed-to-be-unique https://bitbucket.org/codernity/codernitydb/issue/1/_rev-not...
- deleted 14y ago[deleted]
- ecaron 14y agoYou can learn a lot about a community, a product, and a company based on how they respond to bug reports. Promptness, formality, details and politeness are all incredible indicators about what's going on under the hood.
- d0ugal 14y agoAnd what did you make of their reply?
- StavrosK 14y agoBy the way, the risk of a collision with 10 times more members is much more than 10 times as likely, due to the birthday paradox.
- mmcnickle 14y agoYeah, I realised I got the probability wrong but haven't written a follow up (typing on my phone is tough, writing code is impossible). The probability of being able to update an old version of the document, is simply 1/ 65536. That's a very high probability given thousands of documents or a modest number of competing updates. The biggest issue is that it's undetectable and non-deterministic: the update that should fail will succeed silently and it can happen at any time. I'll re-open the bug in the morning with a proof-of-concept.