[pybsddb] Checking put() transaction results: what is the proper way in bsddb3?

[Denis Papathanasiou]

> That's odd...you already got that exception? Here I have only:
> 
>>>> [p for p in dir(bsddb.db) if 'Error' in p]
> ['DBAccessError', 'DBAgainError', 'DBBusyError',
> 'DBCursorClosedError', 'DBError', 'DBFileExistsError',
> 'DBInvalidArgError', 'DBKeyEmptyError', 'DBKeyExistError',
> 'DBLockDeadlockError', 'DBLockNotGrantedError', 'DBNoMemoryError',
> 'DBNoServerError', 'DBNoServerHomeError', 'DBNoServerIDError',
> 'DBNoSpaceError', 'DBNoSuchFileError', 'DBNotFoundError',
> 'DBOldVersionError', 'DBPageNotFoundError', 'DBPermissionsError',
> 'DBRepHandleDeadError', 'DBRepUnavailError', 'DBRunRecoveryError',
> 'DBSecondaryBadError', 'DBVerifyBadError']

In python, my list of exceptions is the same as yours.

DB_READ_UNCOMMITTED is an error specific to transactions, and was 
illustrated in the C example on oracle's site.

So I wondered if there was a pybsddb equivalent, or should I just use 
DBError?