Filenames as separate table vs json array OR multi-valued index at least #1680
metacarejeff
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Maybe I am missing something simple, but is there a reason that the 1:many of scenes:filenames is stored as a json array in a single field?
Matching scenes to known filenames would be a simple inner join and much faster would it not?
Alternatively, https://dev.mysql.com/doc/refman/8.0/en/create-index.html#create-index-multi-valued
That seems like a lot of extra complexity that may not port easily between sqlite and mysql, but I thought I would mention it.
If there is a reason for the embedded json array of possible file names?
Beta Was this translation helpful? Give feedback.
All reactions