findUpdatedScenes

Development
1

any idea if we will get PR#878 merged? I was looking at making a plugin to automatically update scenes with an update on StashDB but the current process of querying makes a single call for each scene, if the plugin were to become popular then a stash-box would get flooded with requests from the plugin, unsure how this would affect performance but I’d rather have official support for such a feature instead of hacking one together

2

I have a work-in-progress tool that has some overlapping functionality with what you’re talking about. It generates batch queries that look like this:

query FindMultipleScenes($id0: ID!, $id1: ID!) {
    s0: findScene(id: $id0) { ...SceneFragment }
    s1: findScene(id: $id1) { ...SceneFragment }
    # And so on...
}

fragment SceneFragment on Scene {
    id
    title
    # And so on...
}

variables = {
    "id0": "6ec1363d-809a-4b57-9006-ed123c27c7d3",
    "id1": "50c7f5b6-fcf5-4344-ba2f-bb329b19d356"
    // And so on...
}

I’m a n00b at graphql, so please forgive any formatting errors or terribleness.

I would imagine that it’s not too overwhelming to the stash-box server because it responds quite quickly, e.g. on StashDB: ~120ms for two scenes and ~1sec for 500 scenes, compared to ~3sec for the graphql query that the stash-box front end itself executes for the default “Scenes” page.

3

I would imagine that it’s not too overwhelming to the stash-box

it would mostly depend on how well the findScene query performs, I just don’t want to publish something that could overwhelm the stash-boxes out there without finding out first

it would also limit the amount of comparing I’d have to do on the client side which is nice but the PR is there so I thought I’d ask

1 Like
4

@Infinite any plans?