# Reverse Index is not ticked, even though @hasInverse is used

**URL:** <https://discuss.dgraph.io/t/reverse-index-is-not-ticked-even-though-hasinverse-is-used/7301>\
**Category:** Users\
**Tags:** graphql\
**Created:** [June 21, 2020, 10:25am UTC](https://discuss.dgraph.io/t/reverse-index-is-not-ticked-even-though-hasinverse-is-used/7301 "2020-06-21T10:25:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![abhijit-kar](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/abhijit-kar/32/3726_2.png) [@abhijit-kar](https://discuss.dgraph.io/u/abhijit-kar)\
**Post date:** [June 21, 2020, 10:25am UTC](https://discuss.dgraph.io/t/reverse-index-is-not-ticked-even-though-hasinverse-is-used/7301/1 "2020-06-21T10:25:45Z")

</div>

Hi Team,

**I used @hasInverse properly, i.e. it works with GraphQL:**

```auto
type User {
    saved: [Post!] @hasInverse(field: savedBy)
}

interface Post {
    id: ID!
	savedBy: [User!] @hasInverse(field: saved)
}

type Illustration implements Post {
}

```

**However, the Ratel UI doesn’t say so:**

![Screenshot from 2020-06-21 15-55-05](https://canada1.discourse-cdn.com/flex007/uploads/dgraph/original/2X/7/786b25eb3c5da8b91dc1febbdd1b82a8e6237cc9.png)

---

<div class="post-metadata">

**Author:** ![anargu](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/anargu/32/5058_2.png) [@anargu](https://discuss.dgraph.io/u/anargu)\
**Post date:** [September 26, 2020, 4:10pm UTC](https://discuss.dgraph.io/t/reverse-index-is-not-ticked-even-though-hasinverse-is-used/7301/2 "2020-09-26T16:10:55Z")

</div>

I have the same problem. There are any news about this issue?

---

<div class="post-metadata">

**Author:** ![MichelDiz](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/micheldiz/32/11873_2.png) [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)\
**Post date:** [September 26, 2020, 4:27pm UTC](https://discuss.dgraph.io/t/reverse-index-is-not-ticked-even-though-hasinverse-is-used/7301/3 "2020-09-26T16:27:19Z")

</div>

The implementation of hasInverse doesn’t use the native reverse index. That’s something that @pawan would explain better.

---

<div class="post-metadata">

**Author:** ![amaster507](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/amaster507/32/4123_2.png) [@amaster507](https://discuss.dgraph.io/u/amaster507)\
**Post date:** [September 26, 2020, 5:21pm UTC](https://discuss.dgraph.io/t/reverse-index-is-not-ticked-even-though-hasinverse-is-used/7301/4 "2020-09-26T17:21:46Z")

</div>

He explained it already over here

> [@hasInverse and how its different from using @reverse on predicates](http://discuss.hypermode.com/t/hasinverse-and-how-its-different-from-using-reverse-on-predicates/9284):
>
> Users of GraphQL± would know that we have @reverse index that allows you to automatically create [reverse edges](https://dgraph.io/docs//query-language/schema/#reverse-edges). In GraphQL, we have @hasInverse. type Author { ... posts: [Post] @hasInverse(field: author) } type Post { ... author: Author } So adding a post for an author also adds the author for the post and vice versa. Under the hood, this is not implemented using @reverse index. There are two separate predicates created here, i.e. Author.posts: [uid] Post.author: uid. Thi…

Let us know where you stand after reading that.