# Real inverse relation on GraphQL schema

**URL:** <https://discuss.dgraph.io/t/real-inverse-relation-on-graphql-schema/7336>\
**Category:** GraphQL\
**Tags:** graphql\
**Created:** [June 23, 2020, 5:20pm UTC](https://discuss.dgraph.io/t/real-inverse-relation-on-graphql-schema/7336 "2020-06-23T17:20:41Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Luscha](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/luscha/32/3588_2.png) [@Luscha](https://discuss.dgraph.io/u/Luscha)\
**Post date:** [June 25, 2020, 1:38pm UTC](https://discuss.dgraph.io/t/real-inverse-relation-on-graphql-schema/7336/6 "2020-06-25T13:38:22Z")

</div>

I guess that some guidance to bulk import using graphql would be nice.

Unfortunately today I also discovered that is not possible to use the reverse edge solution combined with interfaces.

```auto
type Object {
   ownedBy: Person @dgraph(pred: "Object.owner")
}

type BusinessMan implements Person {
  companyName: String
}

interface Person {
    name: String
    owns: [Object] @dgraph(pred: "~Object.owner")
} 

```

Leads to an error because when Car is expanded it expect “ownedBy”'s edge to be an edge of type BusinessMan

```auto
couldn't rewrite mutation updateGQLSchema because input:1: Type Object; Field ownedBy: should be of type BusinessMan to be compatible with @dgraph reverse directive but is of type Person.\n

```

Honestly i feel like interfaces present way too much issue when trying to use the full potential of dgraph combining GraphQL+/- and GraphQL

---

_[View the full topic](https://discuss.dgraph.io/t/real-inverse-relation-on-graphql-schema/7336)._