migrations: split jmdict lookup tables from jmdict schema

migrations/0001_JMDict.sql

@@ -226,26 +226,3 @@ CREATE TABLE "JMdict_ExampleSentence" (
   "japanese" TEXT NOT NULL
   -- "type" TEXT NOT NULL DEFAULT "tat",
 );
-
--- These tables are for optimizing searches.
-
--- In order to include results from both, the software should
--- first check if the searchword is convertible to kana, and then
--- potentially get results from both by doing a union between two
--- selects.
-
-CREATE TABLE "JMdict_EntryByKana" (
-  "kana" TEXT NOT NULL,
-  "entryId" INTEGER NOT NULL REFERENCES "JMdict_Entry"("id"),
-  PRIMARY KEY ("kana", "entryId")
-) WITHOUT ROWID;
-
-CREATE INDEX "JMdict_EntryByKana_byKana" ON "JMdict_EntryByKana"("kana");
-
-CREATE TABLE "JMdict_EntryByEnglish" (
-  "english" TEXT NOT NULL,
-  "entryId" INTEGER NOT NULL REFERENCES "JMdict_Entry"("id"),
-  PRIMARY KEY ("english", "entryId")
-) WITHOUT ROWID;
-
-CREATE INDEX "JMdict_EntryByEnglish_byEnglish" ON "JMdict_EntryByEnglish"("english");

migrations/0007_JMdict_Entry_lookup_tables.sql

@@ -0,0 +1,22 @@
+-- These tables are for optimizing searches.
+
+-- In order to include results from both, the software should
+-- first check if the searchword is convertible to kana, and then
+-- potentially get results from both by doing a union between two
+-- selects.
+
+CREATE TABLE "JMdict_EntryByKana" (
+  "kana" TEXT NOT NULL,
+  "entryId" INTEGER NOT NULL REFERENCES "JMdict_Entry"("id"),
+  PRIMARY KEY ("kana", "entryId")
+) WITHOUT ROWID;
+
+CREATE INDEX "JMdict_EntryByKana_byKana" ON "JMdict_EntryByKana"("kana");
+
+CREATE TABLE "JMdict_EntryByEnglish" (
+  "english" TEXT NOT NULL,
+  "entryId" INTEGER NOT NULL REFERENCES "JMdict_Entry"("id"),
+  PRIMARY KEY ("english", "entryId")
+) WITHOUT ROWID;
+
+CREATE INDEX "JMdict_EntryByEnglish_byEnglish" ON "JMdict_EntryByEnglish"("english");