| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
when using the -3 flag. Patch by Florent Xicluna.
|
| |
|
|
|
| |
Closes issue 3776.
Review by Nick Coghlan.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This patch publishes the work done until now
for Python 3.0 compatibility. Still a lot
to be done.
When possible, we use 3.0 features in Python 2.6,
easing development and testing, and exposing internal
changes to a wider audience, for better test coverage.
Some mode details:
http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.7.2
|
| |
|
|
|
|
|
| |
when database changes size during iteration.
It now behaves like a dictionary, the next attempt to get a value from
the iterator after the database has changed size will raise a RuntimeError.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
now works reliably. It has been updated to use automatic BerkeleyDB
deadlock detection and the bsddb.dbutils.DeadlockWrap wrapper to retry
database calls that would previously deadlock. [SF python bug #775414]
|
| |
|
|
| |
tests this time.
|
| |
|
|
|
| |
DBDeadLockError exception.
* add the test case for my previous dbtables commit.
|
| |
|
|
|
|
|
|
|
| |
bsddb.*open() methods cachesize parameter wouldn't work (raised an
internal bsddb.db exception when it was given). The set_cachesize
call needed to be moved from the DB object to the DBEnv since the env
was introduced to allow for threading.
(will backport to 2.4)
|
| |
|
|
|
|
|
| |
Using None for a filename with the 'n' flag when calling bsddb.btopen
would cause an error while checking if the file None existed. error
not likely to be seen as anyone using None for a filename would likely
use the 'c' flag in the first place.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
It now returns "{}". Is that the correct solution?
|
| | |
|
| |
|
|
| |
Backported to 2.4.
|
| |
|
|
|
|
| |
opening the DB to implement legacy interface flag='n' support as
BerkeleyDB 4.2.52 no longer allows it in transaction protected
environments. Do the os.unlink ourselves.
|
| |
|
|
|
|
|
|
|
| |
* Fixed a bug in the compatibility interface set_location() method
where it would not properly search to the next nearest key when
used on BTree databases. [SF bug id 788421]
* Fixed a bug in the compatibility interface set_location() method
where it could crash when looking up keys in a hash or recno
format database due to an incorrect free().
|
| |
|
|
| |
test_basics.py: updated for the set_get_returns_none() default of 2 change.
|
| |
|
|
|
|
|
|
|
|
| |
memory leak that would've occurred for all iterators that were
destroyed before having iterated until they raised StopIteration.
* Simplify some code.
* Add new test cases to check for the memleak and ensure that mixing
iteration with modification of the values for existing keys works.
|
| |
|
|
|
| |
* Add support for multiple iterator/generator objects at once on the simple
bsddb _DBWithCursor interface.
|
| |
|
|
|
|
|
| |
db that is opened. DB_THREAD and DB_INIT_LOCK allow for multithreaded
access. DB_PRIVATE prevents the DBEnv from using the filesystem
(making it only usable by this process; and in this implementation
using one DBEnv per bsddb database)
|
| |
|
|
|
|
|
|
|
|
| |
features in BerkeleyDB not exposed. notably: the DB_MPOOLFILE interface
has not yet been wrapped in an object.
Adds support for building and installing bsddb3 in python2.3 that has
an older version of this module installed as bsddb without conflicts.
The pybsddb.sf.net build/packaged version of the module uses a
dynamicly loadable module called _pybsddb rather than _bsddb.
|
| |
|
|
| |
adding the iterator interface for python >= 2.3.
|
| |
|
|
| |
iteritems() is defined.
|
| |
|
|
|
|
| |
Add support for the iterator and mapping protocols.
For Py2.3, this was done for shelve, dumbdbm and other mapping objects, but
not for bsddb and dbhash which were inadvertently missed.
|
| | |
|
| |
|
|
| |
so merge from the bsddb-bsddb3-schizo-branch back to the trunk.
|
| |
|
|
| |
version 4.1.1 and works with up to BerkeleyDB 4.1.25.
|
| | |
|
| |
|
