mugiten/jadb
2
1
Fork 0
Code Issues 61 Pull Requests Actions Activity

jmdict: don't store empty entry scores
All checks were successful
Build and test / build (push) Successful in 8m17s
Details

Browse Source
This commit is contained in:
Oystein Kristoffer Tveit
2026-04-13 18:16:19 +09:00
parent d1a6f39cca
commit 4faf543d6e
3 changed files with 31 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/database.md
View File

@@ -25,4 +25,5 @@ The `JMdict_EntryScore` table is used to store the score of each entry, which is
The table is automatically generated from other tables via triggers, and should be considered as a materialized view.
There is a score row for every single entry in both `JMdict_KanjiElement` and `JMdict_ReadingElement`, split by the `type` field.
<s>There is a score row for every single entry in both `JMdict_KanjiElement` and `JMdict_ReadingElement`, split by the `type` field.</s>
This is no longer true, we now only store the rows for which the score is not `0`. The `type` field is now also virtual, since the `elementId` fields for both kanji and readings are unique to each other.