Manual:Slots table

The slots table represent an n:m relation between revisions and content objects.

A content object can have a specific "role" in one or more revisions.

Each revision can have multiple content objects, each having a different role.

slot_revision_id
Reference to  or .

slot_revision_id and slot_role_id together comprise the primary key.

slot_role_id
Reference to 

slot_content_id
Reference to 

slot_origin
The  of the revision that originated the slot's content.

To find revisions that changed slots, look for <tvar|1>slot_origin = slot_revision_id</>.

Schema
+--+--+--+-+-+---+ +--+--+--+-+-+---+ +--+--+--+-+-+---+
 * Field           | Type                 | Null | Key | Default | Extra |
 * slot_revision_id | bigint(20) unsigned | NO   | PRI | NULL    |       |
 * slot_role_id    | smallint(5) unsigned | NO   | PRI | NULL    |       |
 * slot_content_id | bigint(20) unsigned  | NO   |     | NULL    |       |
 * slot_origin     | bigint(20) unsigned  | NO   |     | NULL    |       |