libpurple/resources/sqlitehistoryadapter/01-schema.sql

Sun, 10 Aug 2025 23:44:08 +0800

author
Gong Zhile <gongzl@stu.hebust.edu.cn>
date
Sun, 10 Aug 2025 23:44:08 +0800
branch
purple_conversation_find_message_by_id
changeset 43309
099e1dfb856b
parent 41804
36c3c3cd2402
permissions
-rw-r--r--

Add Purple.Conversation.find_message_by_id

The method was added so that a protocol or plugin could easily lookup
for the reference for a message. This will be especially useful when a
protocol received a quoted message but only with an id.

CREATE TABLE message_log
(
        protocol TEXT NOT NULL, -- examples: slack, xmpp, irc, discord
        account TEXT NOT NULL, -- example: grim@reaperworld.com@milwaukee.slack.com
        conversation_id TEXT NOT NULL, -- example: #general
        message_id TEXT NOT NULL, -- exampe: 14fdjakafjakl1155
        author TEXT NULL, -- could be null for status messages
        author_name_color TEXT NULL,
        author_alias TEXT NULL,
        recipient TEXT NULL,
        content_type TEXT NULL CHECK(content_type IN ('plain', 'html', 'markdown', 'bbcode')),
        content TEXT NULL, -- must be UTF8 string
        raw_content TEXT NULL, -- the message as came from the protocol
        protocol_timestamp TEXT, -- according to protocol, could be wrong
        client_timestamp DATETIME, -- when it "landed" in libpurple
        log_version INTEGER DEFAULT 1 NOT NULL
);

mercurial