[ZODB-Dev] Inconsistent use of ConflictError

[Chris McDonough]

The conflict errors raised in the Connection class' getstate method are
read conflicts... nothing else (AFAIK) is.

Greg Ward wrote:
> 
> On 16 August 2001, I said:
> > Preliminary patch forthcoming...
> 
> OK, I'm attaching three patches to this message:
> 
>   POSException.patch    bulks out the ConflictError class and adds
>                         ReadConflictError
>   ZODB.patch            fixes Connection.py and ZODB/*Storage.py
>                         to raise ConflictError "correctly"
>   bsddb3Storage.patch   fixes bsddb3Storage/bsddb3Storage/*Storage.py
>                         similarly
> 
> This is *COMPLETELY UNTESTED*.  I need to get back to work, but I wanted
> to post this while it's fresh.  Plus some feedback would be nice.
> 
> Oops, I forgot to try to figure out which conflicts are read conflicts
> -- so ReadConflictError is currently unused.  That needs fixing.
> 
>         Greg
> --
> Greg Ward - software developer                gward@mems-exchange.org
> MEMS Exchange                            http://www.mems-exchange.org
> 
>   ------------------------------------------------------------------------
> 
>    POSException.patchName: POSException.patch
>                      Type: Plain Text (text/plain)
> 
>    ZODB.patchName: ZODB.patch
>              Type: Plain Text (text/plain)
> 
>    bsddb3Storage.patchName: bsddb3Storage.patch
>                       Type: Plain Text (text/plain)

-- 
Chris McDonough                           Zope Corporation
http://www.zope.org                    http://www.zope.com

""" Killing hundreds of birds with thousands of stones """