404378f834
catch the situation where Berkeley DB is used to emulate dbm(3) library
...
functions. In this case, calling dbm.open("foo", "c") actually creates a
file named "foo.db".
2002-08-02 17:12:15 +00:00
e2ae77b8b8
SF patch #474590 -- RISC OS support
2001-10-24 20:42:55 +00:00
30edd2387d
Whitespace normalization.
2001-03-16 08:29:48 +00:00
d74fb6b12a
RISCOS changes by dschwertberger.
2001-03-02 06:43:49 +00:00
58eadbaf12
move import into function to avoid having to add an __all__ list...
2001-03-01 04:13:51 +00:00
3027b15c8e
Add missing 'try:'. Patch by Rob W. W. Hooft, #101071 (closed.)
2000-08-04 08:46:59 +00:00
7a4409c1b2
Added support to recognize Python's internal "dumbdbm" database.
...
This closes bug 200 on Jitterbug.
2000-07-29 05:31:40 +00:00
13a2c279c5
Untabify to pass the -tt test.
2000-02-10 17:17:14 +00:00
cf09a3924f
Skip Montanaro:
...
I guess in 1.5.2 a new module, whichdb, was added that attempts to
divine the nature of a database file. This module doesn't know anything
about Berkeley DB v2 files. In v2, Sleepycat added a 12-byte null pad
in front of the old magic numbers (at least for hash and btree files).
I've been using v2 for awhile and upgrading to 1.5.2 broke all my
anydbm.open calls. I believe the following patch corrects the problem.
1999-06-08 13:13:16 +00:00
b86ba124ea
Support byte-swapped dbhash (bsddb) files. Found by Ben Sayer.
1998-04-28 15:41:03 +00:00
45e2fbc2e7
Mass check-in after untabifying all files that need it.
1998-03-26 21:13:24 +00:00
265b5b3f03
Use new struct which supports standardized sizes
1997-01-11 19:22:11 +00:00
8d12a1bcbc
Function to guess which db package created a database.
1996-07-30 16:30:15 +00:00
Skip Montanaro
Guido van Rossum
Tim Peters
Thomas Wouters
Moshe Zadka
Fred Drake