| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
but looks correct on a casual inspection and hasn't been modified
in the trunk. Does anyone want to review further?]
Ensure we don't write beyond errText. I think I got this right, but
it definitely could use some review to ensure I'm not off by one
and there's no possible overflow/wrap-around of bytes_left.
Reported by Klocwork #1.
Fix a problem if there is a failure allocating self->db.
Found with failmalloc.
|
| |
|
|
|
|
| |
Handle malloc and fopen failures more gracefully.
Klocwork 180-181
|
| |
|
|
| |
Fix memory leak reported by valgrind while running test_subprocess
|
| |
|
|
|
|
| |
Check return result from Py_InitModule*(). This API can fail.
Probably should be backported.
|
| |
|
|
| |
arguments. (reported by Louis Zechtzer)
|
| |
|
|
|
|
|
|
|
| |
methods now allow their database parameter to be None as the
sleepycat API allows.
also adds a testcase.
backport of trunk commit 50889 to 2.4.
|
| |
|
|
|
| |
return correct results. It could previously incorrectly return 0 in some
cases. Fixes SF bug 1493322 (pybsddb bug 1184012).
|
| |
|
|
|
|
|
| |
is called with the (unsupported and unexported in this version) flag DB_ARCH_REMOVE.
also fix a log_list memory leak on error return in the event that python can't create
a new list object.
|
| |
|
|
| |
(backport of trunk commit 43729)
|
| |
|
|
|
|
|
|
| |
Coverity found bug: test result of PyTuple_New() against NULL before use.
and r42891 (thomas.wouters):
Fix gcc 4.0.x warning about use of uninitialized value.
|
| | |
|
| |
|
|
| |
Fix bug #1413192, fix seg fault in bsddb if a txn was deleted before the env.
|
| |
|
|
| |
adds support for compiling against BerkeleyDB 4.4.x
|
| |
|
|
|
| |
fixes pybsddb SF bug id 1215432. DB.associate() would crash when a
DBError was supposed to be raised.
|
| | |
|
| | |
|
| |
|
|
| |
ignoring their transaction (txn) argument.
|
| | |
|
| | |
|
| |
|
|
|
| |
Based on a patch supplied by Ian Ward <ian@arevco.ca> on the pybsddb
mailing list 2004-03-26.
|
| |
|
|
|
| |
Make DBTxn objects automatically call abort() in their destructor if
not yet finalized and raise a RuntimeWarning to that effect.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fix memory leaks revealed by valgrind and ensuing code inspection.
In the existing test suite valgrind revealed two memory leaks (DB_get
and DBC_set_range). Code inspection revealed that there were many other
potential similar leaks (many on odd code error paths such as passing
something other than a DBTxn object for a txn= parameter or in the face
of an out of memory error). The most common case that would cause a
leak was when using recno or queue format databases with integer keys,
sometimes only with an exception exit.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
* 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().
|
| | |
|
| | |
|
| |
|
|
| |
or QUEUE database.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
has been closed" exceptions.
Adds a DBCursorClosedError exception in the closed cursor case for
future use in fixing the legacy bsddb interface deadlock problems
due to its use of cursors with DB_INIT_LOCK | DB_THREAD support
enabled.
|
| |
|
|
| |
of the current value without reading the value itself.
|
| |
|
|
| |
version in the python 2.3.1 tree.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
database environments to use shared memory on systems supporting it.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
|
| |
return a tuple. (this also implies that nobody uses this method; the
bug has been here for a long time)
|
| |
|
|
|
|
|
| |
(sourceforge pybsddb bug #737970).
Also: don't allow other threads to run during calls that invalidate the
DB handle.
|
| |
|
|
| |
to the PyBSDDB project at SourceForge.
|
| |
|
|
|
| |
management. Old code still #ifdef'd out - I may remove this in a sec,
but for now, let's get it in and things passing the tests again!
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
underlying DB has already been closed (and thus all of its cursors).
This fixes a potential segfault.
SF pybsddb bug id 667343
bugfix: close the DB object when raising an exception due to an error
during DB.open. This prevents an exception when closing the
environment about not all databases being closed.
SF pybsddb bug id 667340
|
| |
|
|
| |
closes sourceforge pybsddb bug id 669533.
|