What database architecture?

Question

MySQL

I must say right away that my knowledge of working with the database is rather scarce.
I'm going to use a database to store information about the series, including links to watch these series, the series have about 20 episodes, while there are various options for voice acting / subtitles. And for each series in a certain voice acting, its own link.
Essence of a question: How it is correct to organize architecture of such basis.
I only thought of this option: for each series, make tables for various voice acting options, and inside store links to various episodes in this voice acting. But there are about 1k serials, so there will be a lot of tables and this does not seem like a good solution.
To be honest, I don’t really want to read the theory on the database, so I hope for a more or less ready-made solution, or a link to the material explaining exactly my problem
Thank you.

Answer 1

serials:
- id (1, 2, ...)
- name (Jailbreak, Rick and Morty, ...)
serials_voiceovers:
- id (1, 2, ...)
- name (LostFilm, BaibaKo, .. .)
serials_series:
- id (1, 2, ...)
- serial_id `serials.id` (1, 2, ...)
- number (1, 2, ...)
- voiceover_id `serials_voiceovers.id` ( 1, 2, ...)
- url ( serials.com/rik-i-morti.mp4, ...)

Answer 2

take mongo db and don't worry. All series can be stored in one table