Michael Dunstan wrote at 2006-9-2 10:58 +1200:
> ...
>ConflictErrors are _not_ a mechanism for
>prohibiting attribute assignment because that attribute already
>exists. Instead ConflictErrors are a mechanism to prohibit inadvertent
>concurrent updates of the same attribute. (Or in older ZODB's, eve
On 9/1/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
I'm getting a ZODB.POSException.ConflictError in the following code in a
Custom Zope Product, and I'm hoping someone can enlighten me on how to
fix it.
# nd is a folder with a sub-folder "Categories
# "NDCategory" is a custom Zope product
> how many categories are there and how often does this code get executed?
It's only one user and within one request where this is happening. I'm
using ZEO. There must be something I fundamentally don't understand
about how I assign an attribute to an object in the ZODB. If you have
any insigh
[EMAIL PROTECTED] wrote:
I'm getting a ZODB.POSException.ConflictError in the following code in a
Custom Zope Product,
Google for "ConflictError Zope" and read, a lot. These are to be
expected due to Zope's concurrency model, but if end users are seeing
them then your application needs restru
I'm getting a ZODB.POSException.ConflictError in the following code in a
Custom Zope Product, and I'm hoping someone can enlighten me on how to
fix it.
# nd is a folder with a sub-folder "Categories
# "NDCategory" is a custom Zope product I wrote that does not have
anything called "bogus" defined
