summaryrefslogtreecommitdiffstats
path: root/Lib/bsddb
Commit message (Collapse)AuthorAgeFilesLines
* [Patch #1520904] Fix bsddb tests to write to the temp directory instead of ↵Andrew M. Kuchling2007-01-0511-14/+17
| | | | the Lib/bsddb/test directory
* Support linking of the bsddb module against BerkeleyDB 4.5.xGregory P. Smith2007-01-052-3/+4
| | | | (will backport to 2.5)
* Oops, convert tabs to spacesNeal Norwitz2006-11-211-2/+2
|
* Bug #1599782: Fix segfault on bsddb.db.DB().type().Neal Norwitz2006-11-211-0/+4
| | | | | | | | | The problem is that _DB_get_type() can't be called without the GIL because it calls a bunch of PyErr_* APIs when an error occurs. There were no other cases in this file that it was called without the GIL. Removing the BEGIN/END THREAD around _DB_get_type() made everything work. Will backport.
* This was found by Guido AFAIK on p3yk (sic) branch.Neal Norwitz2006-09-051-1/+1
|
* - pybsddb Bug #1527939: bsddb module DBEnv dbremove and dbrenameGregory P. Smith2006-07-281-6/+31
| | | | | | | methods now allow their database parameter to be None as the sleepycat API allows. Also adds an appropriate test case for DBEnv.dbrename and dbremove.
* - bsddb: multithreaded DB access using the simple bsddb module interfaceGregory P. Smith2006-06-152-31/+39
| | | | | | 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]
* Fix errors found by pycheckerNeal Norwitz2006-06-112-3/+9
|
* pasted set_lk_detect line in wrong spot in previous commit. fixed. passes ↵Gregory P. Smith2006-06-081-1/+1
| | | | tests this time.
* * Turn the deadlock situation described in SF bug #775414 into aGregory P. Smith2006-06-082-0/+11
| | | | | DBDeadLockError exception. * add the test case for my previous dbtables commit.
* - bsddb: the bsddb.dbtables Modify method now raises the proper error andGregory P. Smith2006-06-081-18/+25
| | | | | | | | | 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)
* Add missing svn:eol-style property to text files.Tim Peters2006-06-051-65/+65
|
* * fix DBCursor.pget() bug with keyword argument names when no data= isGregory P. Smith2006-06-052-0/+66
| | | | supplied [SF pybsddb bug #1477863]
* Whitespace normalization.Tim Peters2006-06-051-3/+2
|
* forgot to add this file in previous commitGregory P. Smith2006-06-051-0/+112
|
* * add support for DBSequence objects [patch #1466734]Gregory P. Smith2006-06-052-6/+42
|
* * support DBEnv.lsn_reset() method on BerkeleyDB >= 4.4 [patch #1494902]Gregory P. Smith2006-06-051-2/+8
|
* Whitespace normalization.Tim Peters2006-06-051-2/+2
|
* * support DBEnv.log_stat() method on BerkeleyDB >= 4.0 [patch #1494885]Gregory P. Smith2006-06-052-0/+10
|
* bugfix: when log_archive was called with the DB_ARCH_REMOVE flag presentGregory P. Smith2006-06-051-0/+3
| | | | | | | in BerkeleyDB >= 4.2 it tried to construct a list out of an uninitialized char **log_list. feature: export the DB_ARCH_REMOVE flag by name in the module on BerkeleyDB >= 4.2.
* BaseThreadedTestCase.setup(): stop special-casing WindowsError.Tim Peters2006-05-111-2/+0
| | | | | Rev 45964 fiddled with WindowsError, and broke test_bsddb3 on all the Windows buildbot slaves as a result. This should repair it.
* Handle ERROR_ALREADY_EXISTS.Martin v. Löwis2006-05-061-0/+8
|
* Fixes bug #1117761Gregory P. Smith2006-04-121-7/+9
| | | | | | | | | 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)
* Closes bug #1149413Gregory P. Smith2006-04-121-1/+1
| | | | | | | 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.
* Fix bsddb.db.DBError derived exceptions so they can be unpickled.Gregory P. Smith2006-04-082-0/+76
| | | | | Also adds some backwards compatibility when compiling _bsddb.c on earlier python versions (needed for pybsddb).
* Plug the last 657 referenceleaks in test_bsddb3: a circular referenceThomas Wouters2006-03-121-0/+5
| | | | | | | between a TestCase instance, the database it opened (or a cursor to a database) and a bound method as a registered database callback, and a lack of GC-handling in bsddb caused the TestCases to linger. Fix the test, for now, as backward compatibility makes adding GC to bsddb annoying.
* Whitespace normalization.Tim Peters2006-02-201-1/+1
|
* Bug #1210377: close bsddb cursor correctly after NotFoundError.Georg Brandl2006-02-201-1/+4
|
* Add a unit test for bug fix #1396678.Georg Brandl2006-02-192-6/+11
|
* Bug #1396678: a closed bsddb.DB raises AttributeError on repr().Georg Brandl2006-02-191-1/+4
| | | | It now returns "{}". Is that the correct solution?
* fix test import for use in standalone pybsddb project bsddb3 module as wellGregory P. Smith2006-01-291-1/+6
| | | | as python builtin bsddb.
* Add wrapper for DBEnv.set_tx_timeout method to allow time based DB_RECOVERGregory P. Smith2006-01-272-0/+5
| | | | (test cases and dbobj wrapping)
* Fix bug #1413192, fix seg fault in bsddb if a txn was deleted before the env.Neal Norwitz2006-01-252-0/+22
| | | | Will backport.
* Get BSD DB working most for version 3.2Neal Norwitz2005-10-201-0/+2
|
* fix import to work with either module name.Gregory P. Smith2005-06-091-1/+6
|
* Tools/scripts/reindent.py _is_ your friendAnthony Baxter2005-06-084-116/+116
|
* fix more Errors (not Failures) when run using BerkeleyDB <= 4.0Gregory P. Smith2005-06-061-4/+13
|
* fix Errors (not Failures) in test cases when running with BerkeleyDB<4.2Gregory P. Smith2005-06-061-32/+61
|
* make the tests that expect uncatchable exceptions from a callback testGregory P. Smith2005-06-061-19/+48
| | | | | | for them in a roundabout way (catching and parsing stderr) keeps test output clean.
* test case for pybsddb SF bug id 1215432Gregory P. Smith2005-06-061-0/+50
|
* test DB.associate using transactions. somewhat related to SF pybsddbGregory P. Smith2005-06-061-12/+46
| | | | bug #1215432
* pybsddb 4.3.2:Gregory P. Smith2005-06-042-9/+33
| | | | | | | | | | | * the has_key() method was not raising a DBError when a database error had occurred. [SF patch id 1212590] * added a wrapper for the DBEnv.set_lg_regionmax method [SF patch id 1212590] * DBKeyEmptyError now derives from KeyError just like DBNotFoundError. * internally everywhere DB_NOTFOUND was checked for has been updated to also check for DB_KEYEMPTY. This fixes the semantics of a couple operations on recno and queue databases to be more intuitive and results in less unexpected DBKeyEmptyError exceptions being raised.
* Whitespace normalization.Tim Peters2005-06-031-186/+186
|
* pybsddb 4.3.1, adds support for DB.set_bt_compare database btree comparisonGregory P. Smith2005-06-033-0/+218
| | | | | | functions written in python. contributed by <frederic.gobry@epfl.ch>
* Patch #1112812: Make bsddb/__init__.py more friendly for modulefinder.Martin v. Löwis2005-03-031-2/+2
| | | | Backported to 2.4.
* Simplify string comparison using startswith()Steve Holden2005-02-021-1/+1
|
* Purged Berkeley code of references to the long-obsolete whrandom.Tim Peters2004-08-083-5/+4
|
* Whitespace normalization, via reindent.py.Tim Peters2004-07-181-3/+3
|
* Adds support for DB.pget and DBCursor.pget methods.Gregory P. Smith2004-06-282-0/+27
| | | | | Based on a patch supplied by Ian Ward <ian@arevco.ca> on the pybsddb mailing list 2004-03-26.
* SF patch / bug #967763Gregory P. Smith2004-06-271-0/+9
| | | | | | | | | | | | 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.