Delete importFile() and exportFile().  They always raised an
    exception, and there are no subclasses that provide an
    implementation.  I suspect they were decoys from the days
    before export/import was implemented on the Connection.
Remove UndoLogCompatible base class from DB, because it doesn't
    provide the undoLog() method needed to make it at all useful.
Deprecate all the cache_deactivate_after methods.
Replace list2dict with new dict.fromkeys() constructor.
Make imports global instead of local.
Add epydoc markup to DB class docstring.

It's harder to write serious tests, because some of the critical
correctness issues relate to concurrency.  We'll have to depend on the
various concurrent updates and NZODBThreads tests to handle these.

Import IPersistent so docstrings can refer to it.
Move $Id$ tag about @group tags so epydoc doesn't complain.
Don't return anything from _setDB().  The caller always has the object
    anyway.
Rename local variable in register() from object to obj to avoid
    shadowing builtin name.

Please do not only run the unit tests after changes; also test whether
Z3 starts up...

Add get() as preferred synonym for __getitem__.  Change several uses
    of subscripting to get().
Change add() to register new object with transaction.
Change several methods to raise RuntimeError if they are called when
    the Connection is closed.
Add experimental epydoc markup to doc strings.
Extend doc strings and write new tests for "User Methods."

However, fixing it so far *appears* to fix a bunch of shy FileStorage
pack[Now]WhileWriting test failures whose connection to loadBefore()
isn't obvious.  It's plausible that it's a real fix for those, just
not (yet) compelling.  It seems very likely to be a real fix for very
rare failures that have shown up only in ChrisM's overnight testrunner
reports (because those did have stuff related to loadBefore() in their
tracebacks).

TRANS_HDR; also fix an import issue deriving from the creation of
ZODB.FileStorage.format. Problem pointed out by Martijn Faassen
<faassen@infrae.com>. r=jeremy

been broken by a unicode user value.

Broken objects are objects who's class has gone away, typically
because modules or classes have been removed or moved.

Broken objects are objects who's class has gone away, typically
because modules or classes have been removed or moved.

on the Zope 2 head. While I can appreciate the desire to unserstand
why register would be called by an object that has no _p_oid,
such questions should be answered in a sandbox, without breaking the
head.

revise words about registering with transactions.

If an error occurs while unpickling records, a message will be logged
and the affected records are skipped.

Remove the index file after creation. I need to look at this some
more. Why is the saved alias file incorrect? Why isn't the bogosity
recognized when the file is opened?

for each transaction.  Now they are tracked globally.

during converesion. We now skip affected records and output error
messages.