I have a somewhat large (~5TB) pornography collection.
I'd like to make a database with all the proper tags for easy location of content. I have experience with MySQL, but would PostgreSQL would be better for something like this? What about NoSQL?
I'm thinking about a table for each actress with the vendor ID (ie. AUKG-240) of the JAVs as the primary key, and then a separate table for tags that will be linked as a foreign key for each table. Is this a good idea?
Other urls found in this thread:
github.com
danbooru.donmai.us
youtube.com
tagspaces.org
twitter.com
First step is admitting you have a problem.
>He doesn't have a large pornography folder.
How does it feel by having your masturbatory needs cucked by society?
Surely vendor ID would not be unique, right?
A good idea would be killing yourself.
It is.
Have fun destroying your intimate life and turning yourself into a lifeless zombie
>5tb
>'somewhat large'
No motherfucker, that is excessive.
>Not just putting it in the metadata
>I'm thinking about a table for each actress with the vendor ID (ie. AUKG-240) of the JAVs as the primary key,
You're better off using an AUTO_INCREMENT field for your primary key.
>and then a separate table for tags that will be linked as a foreign key for each table
I should be a tags table and an intermediary jav_has_tag table containing a pair of (fk_tag, fk_jav) foreign keys since you're dealing with a many-to-many relationship here
As for noSQL, you could take a look at RethinkDB which is nice and create one document per JAV that you can modify however you want if you don't want to deal with having a strict schema.
You probably won't need a huge DB anyway, 5TB of jav is what? Less than 10k titles? Even sqlite would be powerful enough to manage that.
It used to be much bigger.
Thank you for the serious answer.
AUTO_INCREMENT is basically just assigns a number to each row, right?
>intimate life
... I don’t follow?
How does it feel not getting laid?
>AUTO_INCREMENT is basically just assigns a number to each row, right?
Right, and it should be unique (but this may depend on your database. RTFM)
Basically you want something like this to have an arbitrary number of tags and actresses assigned to your jav entries. I hope you like joins :^) (note that for the intermediary tables, the primary key is the fk pair)
t. EXPERT DATABASE DESIGNER (has designed over 300+ databases)
You niggers step your game up and use javmoviescraper.jar
Scraped through 4tb of Jav
>How does it feel not getting laid?
You sound like a beta orbiter that's butthurt at the fact someone masturbates or watches porn.
>5TB
See
Indifferent and std free.
This is an image database system that lets you view and tag images
github.com
This is an example of the database in action
danbooru.donmai.us
Although it's 5TB of video, I really doubt it's that much in terms of metadata - probably a raspberry pi could handle all of it. Definitely not enough to consider NoSQL retardedness.
Have you thought of using a developed app for it like Plex? Probably what you want without too much effort.
Thanks, user.
I'm mostly just using as a learning experience.
but... with NoSQL, you can just POST ye JSON.
{
"id": "JAV-007"
"vendor": "MYVENDOR",
"tags": [
"guro",
"gal"
]
}
And i though my near 1TB was huge, you're on a completely different level, you should build a dedicated home porn server at that point maybe even make the jump to a SAN
Do you have nice recommendations (books, tutorials) on DB design and development?
Yes, but if you want to assign a tag to a jav for example then you have no guarantee that you didn't make a typo unless you have a separate table of allowed tags to manually compare your insertions to.
Also a well-structured SQL DB is much more convenient and safe to program things on top of, in my opinion.
I know this is nitpicking but I don't have anything in particular against NoSQL DBs that aren't mongo. Rethink is based.
No, I learned most of this in school.
I found this which looks pretty similar to what my courses looked like.
youtube.com
Why not just use this
tagspaces.org
I am not OP but thank you user, this might come in handy.
Yeah, but that's left to the application to make that validation before writing to the database. Users can also always accidentally create new tags as well.
At least in my experience, most customers never know what they actually want to it ends up being a waste of time spending all that time completely architecting your data model. Just implement something that works - or switch to a RDB later after you have a working prototype that the customer likes.
>5TB of porno
pretty sure this thread has appeared before.
I think using the vendor ID as primary key was the right idea - the only reason it wouldn't work would be if there were videos without vendor IDs. Int auto_increment is just a good default when you don't want to put too much thought into it.
And yes, use sqlite
>somewhat large
>5TB
Kek