Multi-Content Revisions/Database Schema

This is an overview over the database schema for representing multi-content revisions.

See the Glossary for the intended meaning of the terms used in this document.

Note that MCR can use ExternalStore directly by using the appropriate URL in, bypassing the text table entirely.

Also, it was suggested that the text table could become the  table, instead of being referenced from the   table.

Name Tables
All name tables (, etc) have the same structure: The table must allow lookups in both directions. Both columns are unique. The id is auto-incrementing.

The mapping defined by the table may be cached aggressively. The mapping should update automatically when attempting to look up the id for an unknown name.