Maybe you want to open a feature request so we can keep track of the progress: https://github.com/graphcool/feature-requests/issues

Thanks @sorenbs, I created https://github.com/graphcool/feature-requests/issues/20. I think this is an essential feature 😊 Without it, we need to filter things client-side, which defeats the purpose of GraphQL... Do you know any other workaround meanwhile?

Indeed! Filtering client side is an obvious workaround and probably what I would go for as that is really easy to remove again when we introduce relation filters. So if you don't anticipate too much data in the next few weeks I would go with that. An alternative is to maintain a separate field on the user that contains either the trackCount for the user, or just a boolean hasTracks. This is a general technique that I often use in high scale systems where it can be desirable to make your writes a little more expensive in order to make reads much cheaper.

Great, thanks @sorenbs for the ideas

Hi any kind person in here got an invite?

Hey @elitan! We'll invite the next batch of early access users shortly!

Thanks for your patience! 🙂

alright

I'll sit tight

hi, the support for Auth0 is available?

Hi @thienpow We will be rolling it out during next week. If you would be interested in helping us test the integration I can set you up manually today.

ya, would love to test it out. how do i setup manually?

I'll send you a pm 🙂

👍

Hey! As many of you <!here|@here> asked: We just added support for nested mutations. This should simplify many cases! https://blog.graph.cool/improving-dx-with-nested-mutations-af7711113d6#.dhagehd4i

hi i saw that you have implemented createdAt and updatedAt, but my old models like user do not have it, how to add those 2 fields?

Hi @thienpow I'll enable those fields for your existing models

thanks!

just to make sure, is there any way to use graph.cool without waiting for an invite? Paid or for free, doesn't matter. And if not, when can we expect next round of invitations? I'm asking because I have a request for project that would use graph.cool

Hey @kenan.selimovic and everybody else <!here|@here> who recently joined. We'll send out the next round of invites shortly. Thanks for your message!

@schickling thanks

Hey Guys! Quick question: this graphql query works in the graphqli tool but with relay it pukes:

countries(limit:3, where:{active:true}){
				  	id,
				  }

Is this a transpiling issue or relay doesn't support objects as parameter?

Hey @peet86! Which Graphcool endpoint are you using for your project?

@schickling I joined 8/18, but got no invitation yet. Was there some issue, or is ~2 months (or more?) the current waiting queue time?

Oh I'm really sorry about this @iki! I'll make sure to activate your invite as soon as possible!

@schickling thank you!

@peet86: afaik there is no where filter, (couldn't find any docs). Are you sure where: is not ignored by graphqli? How does your type definition looks like?

Good catch @redcom It should be

countries(first:3, filter:{active:true}){
                      id,
                  }

Could you give that a try @peet86

(both

limit

and

where

has to be changed)

Hi! How can I get an early access code?