Tigase Unified Archive component uses few tables and stored procedures and it shares same tables with Tigase Message Archiving component - in fact it uses same tables with addition of few fields.
Due to that used tables are prefixed with tig_ma_
, but used stored procedures are prefixed with Tig_UA_
.
This table stores all jids related to stored messages and events, ie. from to
and from
attributes of archived stanzas.
Field | Description | Comments |
---|---|---|
jid_id | Database ID of a JID | |
jid | Value of a bare JID | |
jid_sha1 | SHA1 value of lowercased bare JID | Used for proper bare JID comparison during lookup. (Not exists in PostgreSQL schema) |
domain | Domain part of a bare JID | Stored for easier lookup of messages owned by users of a particular domain |
Table stores archived events.
Field | Description | Comments |
---|---|---|
msg_id | Database ID of a event | |
owner_id | ID of a bare JID of a event owner | References |
buddy_id | ID of a bare JID of a event recipient/sender (different than owner) | References |
buddy_res | Resource part of a event recipient/sender JID | |
ts | Timestamp of a event | Timestamp of archivization or delayed delivery |
direction | Direction of event | 0 - sent by owner 1 - recevied by owner |
type | Stanza type | Value of message |
body | Body of a message | |
msg | Serialized event | |
stanza_hash | Hash of event parts | It is used to make sure that event is stored only once |
item-type | Event type | May be one of: |
offline | Marks offline events | It is set to 1 when it stores offline event, not yet delivered to client |
Table stores tags of archived messages. It stores one tag for many messages using tig_ma_msgs_tags
to store relation between tag and a message.
Field | Description | Comments |
---|---|---|
tag_id | Database ID of a tag | |
owner_id | ID of a bare JID of a tag owner | ID of bare JID of owner for which messages with this tag were archived |
tag | Actual tag value |