![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
| Tue, 21 May 2002 05:52:11 +0000 (05:52 +0000) | ||
| committer | richard <richard@57a73879-2fb5-44c3-a270-3262357dd7e2> | |
| Tue, 21 May 2002 05:52:11 +0000 (05:52 +0000) | ||
| commit | 8bcea6bf45dbbaa8d48c7ef104264f67f6d9e774 | |
| tree | 9174ce518970c4185013efe2757cfc3ae46a1bce | tree | snapshot |
| parent | 5de2f2bba891d8ba2dc0dcc93d80022f8ce05b19 | commit | diff |
Well whadya know, bsddb3 works again.
The backend is implemented _exactly_ the same as bsddb - so there's no
using its transaction or locking support. It'd be nice to use those some
day I suppose.
git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@739 57a73879-2fb5-44c3-a270-3262357dd7e2
The backend is implemented _exactly_ the same as bsddb - so there's no
using its transaction or locking support. It'd be nice to use those some
day I suppose.
git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@739 57a73879-2fb5-44c3-a270-3262357dd7e2
| CHANGES.txt | diff | blob | history | |
| roundup/backends/back_bsddb3.py | diff | blob | history | |
| test/test_db.py | diff | blob | history |