| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
- fixes various memory leaks found by valgrind and a follup closer
code inspection of the bsddb module. (merges r1.32 of _bsddb.c
and an associated test case)
- also merges the one line r1.37 _bsddb.c fix that fixes a leak on
the rare DBEnv creation failed error path.
|
| |
|
|
|
|
|
| |
the end of a second function whos code was identical enough for patch
not to reject the patch. this reverses that misapplication (only the
DBC_set_range method needed modification, not DBC_set as well). This
problem only exists in the release32-maint branch.
|
| |
|
|
|
|
| |
revision 1.17.4.1
date: 2003/11/03 21:37:43; author: greg; state: Exp; lines: +9 -9
* SF patch 835100 - C++ // comments are not allowed. use /* */
|
| |
|
|
| |
their txn argument.
|
| |
|
|
| |
free() on something it did not allocate for non B-Tree based databases.
|
| |
|
|
|
|
|
|
|
| |
* 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().
|
| |
|
|
|
|
| |
is a partial version of the 1.18->1.19 patch. i left out the ability for
the module to also load as _pybsddb in addition to _bsddb as that applies
more to pybsddb than python.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
|
|
|
|
|
| |
coredump or segmentation violation.
Sourceforge patch ID 664896:
http://sourceforge.net/tracker/index.php?func=detail&aid=664896&group_id=13900&atid=313900
The bug was reported on the pybsddb-users mailing list.
|
| |
|
|
| |
version 4.1.1 and works with up to BerkeleyDB 4.1.25.
|
| | |
|
| |
|