Open ZubatyNos opened 10 months ago
@ZubatyNos, this needs clarification.
What do you mean by:
This only happens if there truly no matching entities, otherwise the query works fine
Which entities are you referring to? The folder, or its content?
What does “truly” mean here? There is no folder at all? No content in the folder at all, deleted or not deleted? No folders whatsoever?
Also, is there a pattern to when the two different SPARQL queried are generated? Which one produces which result?
@crnkjck sorry for the inaccuracies.
So I'm referring to the content of the folder and also hwo the subquery filter courses_isDeleted(equals: [false])
comes into play.
So if the main folder has no folderContent
entities that are also set to isDeleted: false
then I should get an empty array from this subquery.
Which I can get, but some of the times I don't even get the main Folder entity.
I can't tell what the pattern for different SPARQL is. The same graphql being queried repeatedly produces this behavior. Seems random to me.
This query should return a Folder with the
folderContent
subquery matching such entities whose valueisDeleted
is set tofalse
. At least I presume.If there are no such subquery entities for
folderContent
, we get a correct result:But sometimes, we don't even get the main entity:
This only happens if there truly no matching entities, otherwise the query works fine
The backend seems to generate SPARQL where the clauses can be ordered differently.
The clauses for fields are ordered differently which seems to be the case for other queries also, but here the entity resolution can be different for some reason.