GraphQL return different number of records when adding fields that is relationship to another entity

[chanhengseang3]

I have this problem: i query a type with field that is basic type, it return correct result. but if i add another field with another type that has relationship to each other then the result may be incorrect.

Here's the use case:

  Clients{
    select{
      firstname
    }
  }
}

returning:

  "data": {
    "Clients": {
      "select": [
        {
          "firstname": "Smith"
        },
        {
          "firstname": "Johnson"
        }
      ]
    }
  }
}

and then

  Clients{
    select{
      firstname
      image{
        id
      }
    }
  }
}

returning

  "data": {
    "Clients": {
      "select": [
        {
          "firstname": "Smith",
          "image": {
            "id": 1
          }
        }
      ]
    }
  }
}

i am expecting:

  "data": {
    "Clients": {
      "select": [
        {
          "firstname": "Smith",
          "image": {
            "id": 1
          },
          {
          "firstname": "Johnson",
          "image": {
            "id": null
          }
        }
      ]
    }
  }
}

I'm not sure my expectation is correct. Please give the argument.

[molexx]

This looks like #101 . The fix for it is in branch igdianov-use-left-outer-join. Please try it to see if it fixes it for you, there is a build on jitpack:

repositories {
    maven { url 'https://jitpack.io' }
    ...
}

dependencies {
    ...
    implementation "com.github.introproventures.graphql-jpa-query:graphql-jpa-query-schema:igdianov-use-left-outer-join-SNAPSHOT"
    implementation "com.github.introproventures.graphql-jpa-query:graphql-jpa-query-annotations:igdianov-use-left-outer-join-SNAPSHOT"
    implementation "com.github.introproventures.graphql-jpa-query:graphql-jpa-query-autoconfigure:igdianov-use-left-outer-join-SNAPSHOT"
    implementation "com.github.introproventures.graphql-jpa-query:graphql-jpa-query-boot-starter:igdianov-use-left-outer-join-SNAPSHOT"
    ...
}

[igdianov]

@chanhengseang3 You can try to use the PR #105 as @molexx suggested. Let me know what you think. I am planning to add support for outer joins using JPA's annotation optional attribute to provide default join behavior with override.

[chanhengseang3]

Thank you!
Problem solved.