| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
be compatible with Python 3.0, also.
http://www.jcea.es/programacion/pybsddb.htm#bsddb3-4.7.3
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
a problem introduced by 58385.
|
| |
|
|
| |
do not contain null bytes.
|
| |
|
|
|
| |
NULL bytes it would cause the database all sorts of problems in the future
leading to very strange random failures and corrupt dbtables.bsdTableDb dbs.
|
| |
|
|
|
| |
keyword argument whenever possible to avoid bugs and confusion. (dbtables.py
line 447 self.db.get using txn as a non-keyword was an actual bug due to this)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
aborts the db transaction safely when a modifier callback fails.
Fixes SF python patch/bug #1408584.
Also cleans up the bsddb.dbtables docstrings since thats the only
documentation that exists for that unadvertised module. (people
really should really just use sqlite3)
|
| | |
|
| |
|
|
| |
From SF patch #852334.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
* Extended DB & DBEnv set_get_returns_none functionality to take a
"level" instead of a boolean flag. The boolean 0 and 1 values still
have the same effect. A value of 2 extends the "return None instead
of raising an exception" behaviour to the DBCursor set methods.
This will become the default behaviour in pybsddb 4.2.
* Fixed a typo in DBCursor.join_item method that made it crash instead
of returning a value. Obviously nobody uses it. Wrote a test case
for join and join_item.
|
| |
|
|
| |
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.
|
| |
|
|
|
| |
prevent close() called from __del__ from bombing out when __init__()
fails early.
|
| | |
|
| | |
|
| | |
|
| |
|
