3
Today I needed to create a table that had a purpose similar to Add the Netflix queue where are saved the movies that the user wants to see (in the application would be stored the urls videos and photos)As soon as I started to create table but I noticed that there was data redundancy and its aesthetics was not cool, so some member has already experienced a similar problem or have any idea how to solve with the least amount of resources possible? remembering that more than one user can have the same movie in the play queue and the queue size is variable
Images of the Tables
the column
data
on the tableVIDEOS
represents what? The date the video was registered?– mateusalxd
yes date of video registration
– Ricardo
What is the aesthetic problem you’re seeing? What do you want to know? What have you tried to do to assemble the missing table? The exercise statement no longer contains any relevant information?
– Maniero
The logic would require a table "n:m" usuarios_videos , relating users to their videos.
– Motta
The problem is that when I created the display queue the data gets duplicated between the lines, another point is that the amount of movies in the display queue is variable EX: user with id:1 has in the queue the movies with id:2, id:7, id: 4, id:3. user with id 2: queued movies with id:5, id:7, id:8.
– Ricardo