From 072eadd89373de6117a8b348b3d26f04edec37f0 Mon Sep 17 00:00:00 2001 From: Athanasius Date: Wed, 28 Sep 2022 17:17:18 +0100 Subject: [PATCH] EDDN: messages.id AUTOINCREMENT, and index created & cmdr We'll definitely want to query against `cmdr`, and possibly `created`. We shouldn't need to against other fields, they'll just be checked during processing of an already selected message. --- plugins/eddn.py | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/plugins/eddn.py b/plugins/eddn.py index 50cb402c..eee9e8d1 100644 --- a/plugins/eddn.py +++ b/plugins/eddn.py @@ -191,7 +191,7 @@ class EDDN: """ CREATE TABLE messages ( - id INT PRIMARY KEY NOT NULL, + id INTEGER PRIMARY KEY AUTOINCREMENT, created TEXT NOT NULL, cmdr TEXT NOT NULL, edmc_version TEXT, @@ -202,6 +202,24 @@ class EDDN: """ ) + replaydb.execute( + """ + CREATE INDEX messages_created ON messages + ( + created + ) + """ + ) + + replaydb.execute( + """ + CREATE INDEX messages_cmdr ON messages + ( + cmdr + ) + """ + ) + except sqlite3.OperationalError as e: if str(e) != "table messages already exists": raise e