What database Architecture?

0 like 0 dislike
17 views
I must say that my knowledge in working with databases is quite poor.

Going to use a database to store information about the series, including links to view these soap operas, the TV series has about 20 episodes, while there are various options of voice/subtitles. And for each series in a definite voice of its own link.

The crux of the matter: How to organize the architecture of such a base.

I was thinking only this: for each series to do the table under the various options of voice and inside to store references to various episodes in this voice. But of series order of 1K, so you get a lot of tables and it doesn't seem like a good solution.

Read a theory on dB, to be honest not very desirable, so I hope for a more or less turnkey solution, or a link to the material rastolkovali exactly my problem
Thank you.
by | 17 views

2 Answers

0 like 0 dislike
serials:
- id (1, 2, ...)
- name (escape from the prison, 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, ...)
by
0 like 0 dislike
take mongo db and do not worry. All serials can be stored in a single table
by

Related questions

0 like 0 dislike
4 answers
0 like 0 dislike
4 answers
0 like 0 dislike
1 answer
110,608 questions
257,186 answers
0 comments
33,932 users