When a database is created "by hand" from a custom_zodb.py during
startup, we still want to put it in the dbtab multidatabases dict.

This happens when unit tests call Zope2.startup(), because Testing has a
specific custom_zodb.py loaded at startup that uses a DemoStorage.

No commit message

phase for FTP and HTTP servers

        (RNFR now returns 350 as status code instead 250)

http://mail.zope.org/pipermail/zodb-dev/2005-December/009662.html
Basic symptom was lots of conflict in sessions.
Unit test included.

  Update Five to bugfix release 1.3.1.

No commit message

in some unittests (if necessary we need to restablish the hacks
in a saner way)