whenever they have less than a page of results. Not that big of deal I suppose, but it just bugs me that there are perpetually a few dozen posts I'm not able to get at.
EDIT: Right after I posted this I thought to use black listing to root out those last few and it worked fine. I can't believe it took me 2 months to think of this. The searches are still borked for me, but it's more or less not a problem for my purposes anymore.
If this is the case, maybe it would be a good idea to move some of the search filtering to the client side officially. We could set the system to do all base tag stuff server side, then winnow things based on metatag and tag negations in the client, much the way the blacklist works now.
There's no way these searches will ever be fast, especially the last three. You're basically searching for posts without a tag. This means checking every single post. It just can't be indexed well.
Danbooru2 will help with the favorite search issue since favorites are being moved to the GIN index. But this is a major schema change and it's not something I'm willing to backport.
I'm getting random failboorus at least once a day through normal browsing and tag edits. I also get a lot of failboorus trying to access JXH's account page. Its only his page, so I don't know what the issue is.
Action_Kamen said: Its been happening a lot, for a long time now. Especially when I'm searching for specific touhou characters in my favorites. For example fav:Action_Kamen reiuji_utsuho, fav:Action_Kamen letty_whiterock and a couple other searches.
Any ideas on what I can do to fix this?
I mentioned it before (forum #55728), if you add order:score or order:favcount to the query, it works for some odd reason. Seems only appy to favorite searches though.
I thinkr2532 might've been responsible for this, as I'm pretty sure I started seeing this problem too right around the time that changeset was commited.
eidolon said: I mentioned it before (forum #55728), if you add order:score or order:favcount to the query, it works for some odd reason. Seems only appy to favorite searches though.
Just tried this for my res tag gardening searches and it worked swimmingly. So there's that.
eidolon said: I mentioned it before (forum #55728), if you add order:score or order:favcount to the query, it works for some odd reason. Seems only appy to favorite searches though.
Probably because then it's not doing the default order-by-favorited-date. Actually, looking at the DB schema just now, the created_at column of the favorites table doesn't appear to have an index.
albert said: There's no way these searches will ever be fast, especially the last three. You're basically searching for posts without a tag. This means checking every single post. It just can't be indexed well.
I filed a ticket about this in the Trac about a year and a half ago, actually. Why are we still doing the absurdres and the like manually rather than adding it automatically on upload?
Just hit on the favourite search problem myself - I noticed I had 5 deleted posts in my favourites and was curious as to what they are but am getting falibooru consistently on fav:wanchan status:deleted.
wanchan said: Just hit on the favourite search problem myself - I noticed I had 5 deleted posts in my favourites and was curious as to what they are but am getting falibooru consistently on fav:wanchan status:deleted.