[Brainfuck]

Originally Posted by buttfacelol

I'm not exactly an expert on databases, but I was originally thinking a mod/artist defined string they could set to just list their favorites. I'm guessing a string would be less of a load on the database than a set of favorites like you're describing? I'm just talking out of my ass, though.

Perhaps, but right now I am keeping it in a relational database. It basically means I have a table of fetishes and a table of 'works' (e.g. illustrations, stories, etc.). Since - in my mind - one 'work' can contain several fetishes, I decided to create a table that links these two tables, which allows several rows per work.

For example, Work A contains Fetish A and B, so in its relation table it contains 2 rows, both indicating Work A but Fetish A and B respectively. Since some fetishes has a value attached (this is where the sliders come in, more on that later), one 'long string' has issues, partly because I need to parse it, which is a lot slower than a relation table in the long run.

Originally Posted by insomniac

I've wanted to do this with SW stuff for a while, but I lack the know-how in actually creating stuff like databases, etc. The thing I'd want is when I login to only see the things I want, i.e my favorite fetishes, then maybe the newest stuff first. It's a bit annoying to go on giantessbooru and see all the stuff I consider crap plastered all over the front page.

That is exactly the intend. Although, you need to define your 'filter' first. The idea is when you are using the filter system (as linked in the original post) there will be a link that says 'set this as my default filter', which means that your front page will from now on show this filter. If a user has no filter (or is not logged in) it will show the default front page.

I even intend to give every user an RSS feed of their filter when created. But so far only one filter per user. I think that should be enough for everyone.

Originally Posted by insomniac

Are you going to break down the transformations as well? I'm a big shrinking fan and seeing other fetishes like transformation and transgender have shrinking in it, so something like being able to select transformations and then list on the ones that have shrinking in them would be awesome.

Since shrinking isn't a 'transformation (other)' fetish (as of right now at least), but rather related to 'body size' (such as growth, giantess, etc.) it will not be listed under transformation fetishes.

However, the filter will allow you to do this. You will be able (in a future version of the filter interface) be able to select 'shrinking' and the fetish category 'transformation (other)'. Which will generate a gallery of images with only shrinking and transformation. I have - however - not developed that as of yet, but due to my relational database, it should be technical rather easy (and fast too).

Remember, a database tends to be far better at handling data than say a regular programming language like PHP or Python. Because that is its purpose!