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.

The basic entity/relationship structure is as follows:

For a discussion of the scalability and efficiency of this design, see Multi-Content Revisions/Content Meta-Data#Database Schema.

Below there is a description of all the tables involved, and comments about what should be done with individual fields. The status column gives a quick indication of what changes a field may undergo, and what decisions are to be made:

Perhaps this should have a better name, such as ? Field prefix would be.

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.