>
> You shoudn't need to be building your own locking system on top of
> ZODB, this suggests that either ZODB is the wrong tool for your
> problem, or that you're using it wrong ;)
>
> ZODB has MVCC which means you get a consistent view of the database
> from the time the transaction was begun (see
On 21 March 2012 22:54, Claudiu Saftoiu wrote:
> Hello ZODB List,
>
> (This is also a stackoverflow question - you might prefer the formatting
> there: http://stackoverflow.com/questions/9810116/zodb-database-conflict-fail )
>
> I have a server, and a client.
>
> A client sends a request. The requ
Hello ZODB List,
(This is also a stackoverflow question - you might prefer the formatting
there:
http://stackoverflow.com/questions/9810116/zodb-database-conflict-fail )
I have a server, and a client.
A client sends a request. The request has a certain key associated with it,
e.g. `a-1`, `a-2`,
