Looks like KnexNest uses the first data as a reference to create Hydration meta data, and Hydration will use it as a reference to distinct the data. I also found that #7 issue related with this.
example:
[{
_id: 1,
_name: "abc",
_child__id:1, //<-- must unique non null
_child__name:"def"
},
{
_id: 1,
_name: "abc",
_child__id:2, //<-- must unique non null
_child__name:"efg"
},]
Looks like KnexNest uses the first data as a reference to create Hydration meta data, and Hydration will use it as a reference to distinct the data. I also found that #7 issue related with this.
example: