d179cb9bdd
This completes the heavy lifting of persisting messages locally. The strategy is that the local database may be sparsely populated, both in the availability of messages in a folder and the fields of a message that is partially stored. As data is pulled from the remote server it's always stored in the database. Future requests will always go to the database first, preventing unnecessary network traffic. Also, this patch will detect when a message is stored in multiple folders on the server. The database uses soft links from the folder to the message, so the message is stored only once in the database. This technique relies heavily on the availability and validity of the Message-ID header, but we expect this to be reliable the vast majority of the time.
107 lines
2.3 KiB
SQL
107 lines
2.3 KiB
SQL
|
|
--
|
|
-- FolderTable
|
|
--
|
|
|
|
CREATE TABLE FolderTable (
|
|
id INTEGER PRIMARY KEY,
|
|
name TEXT NOT NULL,
|
|
parent_id INTEGER REFERENCES FolderTable ON DELETE RESTRICT
|
|
);
|
|
|
|
CREATE INDEX FolderTableNameIndex ON FolderTable(name);
|
|
CREATE INDEX FolderTableParentIndex ON FolderTable(parent_id);
|
|
|
|
--
|
|
-- MessageTable
|
|
--
|
|
|
|
CREATE TABLE MessageTable (
|
|
id INTEGER PRIMARY KEY,
|
|
fields INTEGER,
|
|
|
|
date_field TEXT,
|
|
date_time_t INTEGER,
|
|
|
|
from_field TEXT,
|
|
sender TEXT,
|
|
reply_to TEXT,
|
|
|
|
to_field TEXT,
|
|
cc TEXT,
|
|
bcc TEXT,
|
|
|
|
message_id TEXT,
|
|
in_reply_to TEXT,
|
|
|
|
subject TEXT,
|
|
|
|
header TEXT,
|
|
|
|
body TEXT
|
|
);
|
|
|
|
CREATE INDEX MessageTableMessageIDIndex ON MessageTable(message_id);
|
|
|
|
--
|
|
-- MessageLocationTable
|
|
--
|
|
|
|
CREATE TABLE MessageLocationTable (
|
|
id INTEGER PRIMARY KEY,
|
|
message_id INTEGER REFERENCES MessageTable ON DELETE CASCADE,
|
|
folder_id INTEGER REFERENCES FolderTable ON DELETE CASCADE,
|
|
position INTEGER
|
|
);
|
|
|
|
CREATE INDEX MessageLocationTableMessageIDIndex ON MessageLocationTable(message_id);
|
|
CREATE INDEX MessageLocationTableFolderIDIndex ON MessageLocationTable(folder_id);
|
|
|
|
--
|
|
-- IMAP-specific tables
|
|
--
|
|
|
|
--
|
|
-- ImapFolderPropertiesTable
|
|
--
|
|
|
|
CREATE TABLE ImapFolderPropertiesTable (
|
|
id INTEGER PRIMARY KEY,
|
|
folder_id INTEGER UNIQUE REFERENCES FolderTable ON DELETE CASCADE,
|
|
uid_validity INTEGER,
|
|
supports_children INTEGER,
|
|
is_openable INTEGER
|
|
);
|
|
|
|
CREATE INDEX ImapFolderPropertiesTableFolderIDIndex ON ImapFolderPropertiesTable(folder_id);
|
|
|
|
--
|
|
-- ImapMessagePropertiesTable
|
|
--
|
|
|
|
CREATE TABLE ImapMessagePropertiesTable (
|
|
id INTEGER PRIMARY KEY,
|
|
message_id INTEGER UNIQUE REFERENCES MessageTable ON DELETE CASCADE,
|
|
answered INTEGER,
|
|
deleted INTEGER,
|
|
draft INTEGER,
|
|
flagged INTEGER,
|
|
recent INTEGER,
|
|
seen INTEGER,
|
|
all_flags TEXT
|
|
);
|
|
|
|
CREATE INDEX ImapMessagePropertiesTableMessageIDIndex ON ImapMessagePropertiesTable(message_id);
|
|
|
|
--
|
|
-- ImapMessageLocationPropertiesTable
|
|
--
|
|
|
|
CREATE TABLE ImapMessageLocationPropertiesTable (
|
|
id INTEGER PRIMARY KEY,
|
|
location_id INTEGER UNIQUE REFERENCES MessageLocationTable ON DELETE CASCADE,
|
|
uid INTEGER
|
|
);
|
|
|
|
CREATE INDEX ImapMessageLocationPropertiesTableLocationIDIndex ON ImapMessageLocationPropertiesTable(location_id);
|
|
|