Description Caspar D. 2010-12-30 00:58:58 EST

1. CDOServerImporter.FlushHandler.handleRevision calls accessor.rawStore(..).
DBStore's implementation of this method always calls writeRevision with
argument newRevision == true. But of course, only 1 of the imported revisions
for a specific CDOID can serve as the 'newRevision', i.e. the first for a
new object. For all revisions that get imported later, this throws an exception
when the unique key constraint is violated in the ObjectTypeTable.

2. When the argument is set to newRevision == false in appropriate cases,
the logic in AbstractHorizontalClassMapping.writeRevision(*) that revises
the 'old' revision gets invoked. But it cannot be guaranteed that the 
import order corresponds to the version sequence, so this 'old' revision
might not exist yet.

3. Same as bug 333294 but for DBStore.