New Database Design
Current DB design is simply copying the data on episodes.json and languages.json into a separate table. With this approach I can get supported language with the episode data but not the other way around. Also with the addition of file path in tools#19 (closed) we also need a entry/table to put them in.
Here's the design requirements I see:
- We should be able to get episode id and language code(P&C) when either one is present.
- We should be able to store file paths in a scalable form i.e. not restricted in the number of paths.