Hello Christian, Yeah, uuid was my guess. What about some human-eatable counter-like thing? Btrees have some length with conflict resolution support, but I'm not sure that could be used to make a key and __name__.
Thursday, April 2, 2009, 10:47:07 AM, you wrote: CT> On Thu, 2009-04-02 at 10:19 +0200, Adam GROSZER wrote: >> Hello, >> >> What's a good practice to create unique container keys for a heavily >> loaded application? (I mean lots of writes to the same container) >> Obviously having a counter on the container and incrementing and using >> that for key gives write conflicts. >> >> What do the experts use? CT> If uniqueness is your only concern then using a large number range and CT> consuming numbers randomly will perform better than incrementing. CT> Christian -- Best regards, Adam GROSZER mailto:agros...@gmail.com -- Quote of the day: The golden opportunity you are seeking is in yourself. It is not in your environment; it is not in luck or chance, or the help of other; it is in yourself alone. (Orison Swett Marden) _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev