okay so I'm no DBA here, but I'd attack this problem by using multiple tables and then joining them. You have a main table of videos, which would have the ID, studio, release date, and anything else that there's only one of per video. Then have other tables for the actresses and tags.
You want them to be separate tables so that each (ID, tag) or (ID, actress) pairing doesn't have to be stuffed into one big row in a main table. That way one ID can have as many tags as you care to and you don't have to change the schema if you want to add lots. Similarly you won't have to decide ahead of time how many actresses you can have for one video.
Not OP, but I have one in my garage for years already, got it after it was decommissioned at my last job. Fully kitted out, probably the highest end configuration it can take, some parts not even officially supported by the 250, since it got used well into the early 2010's and upgraded several times. I should clean it up and find a home for it, not particularly interested in using it myself and old Sun hardware isn't that popular or expensive on the market for some reason.
Jacob Johnson
Asian milfs in particular can violate this constraint.
Ayden Wright
>VARCHAR for uuid Get yourself a real database like postgres And use citext while you're at it Too lazy to point out the rest of the flaws
>gratuitously inconsistent key types >personal preferences (favourites, ratings) not stored in separate link tables >pointless link table PK's (without additional constraints, they allow duplicate lines), use composite primary keys (e.g. circle + comic) instead If you have zero college credits on this under your belt, it's not too bad.
Alexander Myers
>gratuitously inconsistent key types Intentional, I generate those outside the db and use the ID's the link tables I use let the db handle the id's as I don't care about them >pointless link tables ... I didn't write the constrains on the ER as I couldn't be bothered and it looks cluttered but the link tables do have uniqueness constrains on the linking ID's.
Asher Anderson
>pointless link tables ... No, I said >pointless link table PK's There are three columns on multiple link tables e.g. >id >circle >comic the id column is redundant. use a composite key (circle + comic) as the primary key instead.
