Prisma

because sometimes you really need the id :slightly_smiling_face:

will I need to do that if I want to create a new family and say that the current user owns it?

then you can do
```
mutation {
  createFamily(userId: "id", title: "My Family") {
    id
  }
}
```

I assume thats possible to enforce with a permission query, make sure that the user id the client passes is the same as $userId?

it's possible with a new exciting feature that we call permission queries

that's available through our beta program and we're rolling it out soon

Awesome, Johannes invited me to that beta the other night :wink:

I think I spelled that right, sorry if not

<!here|@here> I have these query/mutations:

```
const FamiliesQuery = gql`query {
  user {
    id
    ownedFamilies(orderBy: name_ASC) {
      id
      name
    }
  }
}`

const CreateFamilyMutation = gql`
  mutation ($name: String!, $ownerId: ID) {
    createFamily(name: $name, ownerId: $ownerId) {
      id
      name
    }
  }
`

export default (
  graphql(CreateFamilyMutation)(graphql(FamiliesQuery)(FamilyList))
)
```

and in my client: `new ApolloClient({ dataIdFromObject: o =&gt; o.id, networkInterface })`

but when I add a family, I need to reload to see it

is it because `ownedFamilies` and `createFamily` mutation results are cached differently?

Hey <@U3XCLPZPB>, this is caused by the fact that the id of the newly created family is not yet known to Apollo

no, this is not the problem. Using `updateFamily` doesn't show that behaviour, it updates without a reload

There are different options to handle this
* if you don't have a lot of families, you can call `this.props.data.refetch()` in the `then` of the mutation. This refetches the whole query though, which is not performant for a lot of data...
* the efficient way to do it is to define `updateQueries` on the `createFamily` mutation.

Some resources for the second approach:
* <https://www.learnapollo.com/excursions/excursion-02/>
* <http://dev.apollodata.com/react/cache-updates.html#updateQueries>

I was looking at <https://www.learnapollo.com/excursions/excursion-02/> and I realized just now I needed to keep reading:

&gt; While specifying `dataIdFromObject` like that helps when working with queries and updating nodes, we have to do a bit more to make caching consistent in combination with creating or deleting nodes.

I appreciate it! I love feeling like a noob again.

depending on the Apollo client version you're using you might also run into this problem: <https://github.com/apollographql/apollo-client/issues/1129>

```
cat yarn.lock | grep apollo-client
apollo-client@^0.8.1:
```

haven't had the change to check if that works. From what I've seen, this is currently unresolved...