@nilan commented on @sven’s file https://prisma.slack.com/files/U526NK30C/F51U9PMT2/Question_about_GraphQL_queries: Are you talking about this alternative data model

query {
  allUsers {
    houses {
      street {
        id
      }
    }
   streets {
     id
   }
  }
}

@nilan commented on @sven’s file https://prisma.slack.com/files/U526NK30C/F51U9PMT2/Question_about_GraphQL_queries: note the additional connection between

User

and

Street

via the

streets

field

@sven commented on @sven’s file https://prisma.slack.com/files/U526NK30C/F51U9PMT2/Question_about_GraphQL_queries: Yes. Basically references between all three types instead of two references, which is the minimum of references to make sense of the data.

@nilan commented on @sven’s file https://prisma.slack.com/files/U526NK30C/F51U9PMT2/Question_about_GraphQL_queries: I would highly recommend against duplicating data entry points like this. The increased complexity for the query is only slight, but now you would need to do a lot of brittle housekeeping to keep the different connections

user -> houses -> street

and

user -> streets

in sync.

@sven commented on @sven’s file https://prisma.slack.com/files/U526NK30C/F51U9PMT2/Question_about_GraphQL_queries: all right. that’s also what my gut feeling told me. but those nested filters is something I didn’t see anywhere

hello there @lukasz 👋

welcome to our slack

hey, @dmancan 👋 @dmitry welcome to graphcool 🙌

thanks! 👋

I enabled auth0 but i cannot see the users,is there any required step I’m missing?

I'm a little confused with

graphql-relay

and what is going on with this example. Can someone help me understand a few things about it?

This is the code-base I'm looking at: https://github.com/relayjs/relay-examples/tree/master/todo-modern

Hey @rockchalkwushock #stackoverflow is a great place to discuss questions like this 🙂

ok sorry didn't think about looking there. this library is quite different than

graphql

the good news @rockchalkwushock is that you found the place it differs 🙂 beyond that, there’s not much.

Hello everyone 🙂

hello there @equimper 🙌 glad you’re joining us today!

🙂

Did graphcool changed their pricing model recently? It seems the database storage is much less as compare to the the previous pricing model.

@taras @lyonwj hi and welcome to our slack! 👋

Hey, I keep getting

The provided idToken is invalid

when trying to create a user with auth0. I've verified that the idToken is valid and from the right domain/etc. Does anyone have any ideas?

@sophia @mtsmfm @john @sune.niemann hello there and enjoy your weekend with graphcool 👋

I’ve created a channel relate to aws lambdas and serverless for quick questions and discussions, feel free to join #lambda-serverless

I have events which have a link to a location. I have a mutation callback, that should fire when the event with location is known (there's a one-to-many relation between location and event) To add an event with a location, I have to add the location first, the event without location second and than make the relation between event and location. This all works... However, the mutation callback should not be fired when the event is created, since the location is not known at that time - it still is weird graphcool can't handle it to set the relation at creation time, but that's how it is. So I want the mutation callback to fire when I 'update' the location field of the event, the mutation callback is not fired. Apparently, updating a relation between entities is not(!) considered as an update. (Also checking the permissions, e.g.

edit field

, relations are not considered as fields: when I try to set the permission to update the

location

field of an event, I can't: this

location

-field is not shown as a field). How can I make the callback fire only when an event with location is known?

@heres hola, welcome! 🙌 enjoy your weekend with graphcool

hi @kharioki 👋

Hello therr

enjoy your saturday with graphcool @looneydude 👋 (plus points for the name 😃 : )

@nilan Now I found out why I had some doubt regarding the graphcool pricing model earlier. You pricing page on desktop shows a different version as compare to mobile version of the website