header

Reworked version of rev 1.49. Fixes a strange problem with the re module in Python 2.1c1. Works now with the official 2.1 release

the standard Python 2.1 distribution. The asyncore module from
the Medusa package has been removed it is not compatible with the
one shipped with the Python distribution.

Marshalling code still needs to be converted to re
by someone understanding the code :-)

configure for certain kinds of setups.

to override BaseStorage's tpc_vote().  This isn't necessary for any
subsequent Zope distributions, because BaseStorage has grown an
identical tpc_vote.

little more work.  First, we need to delete all the entries for
oid+vid records in the currentVersions table, then if we delete all
thosey vid entries, garbage collect the version->vid and vid->version
tables.

pack(): Fix a slight misunderstanding of the semantics; if an object
isn't pointed to by root object (i.e. the magic \0\0\0\0\0\0\0\0 oid),
then it's current record doesn't keep it alive.

checkCreateWithFilename(), checkCloseDoesUnlink(), checkDel(): Don't
unlink explicitly, but assert that the file is unlinked after close.

BaseSetupTearDown.tearDown(): It's okay if the tear down unlink fails
because the file already doesn't exist.

suite(): Use makeSuite.

should be on close.  By default, we unlink the file unless we were
passed a file-like object, in which case we don't unlink by default
(because the client owns the file).

close(): Only close the file if the file isn't already closed.  Only
unlink if the default unlink flag is true, or we're explicitly told to
unlink via the argument.  This should fix the logfile turd problem.

ZODB.tests (with apologies to Jim for the backslash ;).

ZODB.tests

- Update the CHANGES.txt file.

Usage: requestprofiler.py filename [--sort=spec] [--top=n] [--verbose] [--help]

Provides a profile of the detailed (-M) Zope request log.

Each line in the profile indicates information about a Zope method (URL)
collected via the detailed request log (the -M log).

'filename' is the path to the '-M' log that contains detailed request data.

If a 'sort' value is specified, sort the profile info by the spec. The sort
spec may be any of 'hits', 'hangs', 'max', 'min', 'mean', 'median', or 'total'.
The default is 'total'.  The sort order is decending unless indicated.

  'hits'       -- the number of hits against the method
  'hangs'      -- the number of unfinished requests to the method
  'max'        -- the maximum time in secs taken by a request to this method
  'min'        -- the minimum time in secs taken by a request to this method
  'mean'       -- the mean time in secs taken by a request to this method
  'median'     -- the median time in secs taken by a request to this method
  'total'      -- the total time in secs across all requests to this method
  'url'        -- the URL/method name (ascending)

If the 'top' argument is specified, only report on the top 'n' requests in
the log (as per the sort).  The default is 10.

If the 'verbose' argument is specified, do not trim url to fit into 80 cols."""

table; use a safer way of pulling out the lrevid.

pack(): The previous logic was broken, now we first gather up all the
oids of the objects affected by packable transactions, then we cruise
through the metadata records of each of those in a separate loop.

Watch out for the call to c.set_range() on the txnoids table to raise
a DBNotFoundError.  This just means we're trying to access a time
stamp past the last one in this table, so just use c.last() if that
happens, and pack all transactions.

When cruising through the txnoids table, stop when you see the first
PROTECTED_TRANSACTION.  That means that we've already packed back to
this transaction (Jim, is this right?  Would we ever want to re-pack a
transaction that's already been packed?)