2018-10-13, 18:00
Hi!
I've been using Kodi for a long time, and am quite happy with its capabilities. However, I've found that the DB Tends to accumulate garbage over time - even when I clean it out (Clean Database on Update is on) regularly. I recently had an issue where I had to go spelunking in the DB to fix a broken file (case-sensitivity issue...long story), and realized that there's literally *NO* referential integrity being applied.
I'm wondering if this is by design and there are valid reasons to actively avoid adding it, or if it's simply vestigial and "nobody's gotten around to adding it"
Adding this kind of integrity could speed up many queries *significantly*, but also facilitate cleanup as it's easier to avoid "dangling" records being left over after a library maintenance session (file renames, relocation, etc).
Thanks!
I've been using Kodi for a long time, and am quite happy with its capabilities. However, I've found that the DB Tends to accumulate garbage over time - even when I clean it out (Clean Database on Update is on) regularly. I recently had an issue where I had to go spelunking in the DB to fix a broken file (case-sensitivity issue...long story), and realized that there's literally *NO* referential integrity being applied.
I'm wondering if this is by design and there are valid reasons to actively avoid adding it, or if it's simply vestigial and "nobody's gotten around to adding it"
Adding this kind of integrity could speed up many queries *significantly*, but also facilitate cleanup as it's easier to avoid "dangling" records being left over after a library maintenance session (file renames, relocation, etc).
Thanks!
