Split out Kanji/Reading element's readingDoesNotMatchKanji/news/ichi/spec/gai/nf into separate tables #54

Open
opened 2025-05-22 16:06:36 +02:00 by oysteikt · 1 comment
Owner

With the addition of the "materialized view" in #44, we can now split out these fields into separate tables to avoid storing a bunch of NULLs

With the addition of the "materialized view" in #44, we can now split out these fields into separate tables to avoid storing a bunch of NULLs
oysteikt added the space-reduction label 2025-05-22 16:24:53 +02:00
oysteikt added this to the Kanban project 2025-06-23 10:33:10 +02:00
oysteikt moved this to Low pri in Kanban on 2025-06-23 10:43:42 +02:00
oysteikt added a new dependency 2025-06-23 12:39:27 +02:00
oysteikt changed title from Split out Kanji/Reading element's `news`/`ichi`/`spec`/`gai`/`nf` into separate tables to Split out Kanji/Reading element's `readingDoesNotMatchKanji`/`news`/`ichi`/`spec`/`gai`/`nf` into separate tables 2025-06-25 09:18:23 +02:00
Author
Owner

We're going to need create/update/delete triggers for JMdict_EntryScore on every individual table. I think that should make this issue dependent on #53

We're going to need create/update/delete triggers for `JMdict_EntryScore` on every individual table. I think that should make this issue dependent on #53
Sign in to join this conversation.