Pavol Perdík

@gareth-ib Not sure if Taylor really seees this as an error (reading couple of previouse threads i.e. https://github.com/laravel/framework/issues/5355#issuecomment-115426172). Anyway, is there any progress on adding composite primary keys support for...

We need this very much and can allocate some resources on it. Unfortunately, we're lost where to even start, so we appreciate your help. Do you have an idea, how...

Okay, we've been digging a bit deeper. It looks what we want actually goes against how GraphQL is designed. Each subscriber defines the graphql query specifing what he would like...

Hey, thank you. I've been doing some testing. I have extracted the pusher calls into jobs and run them in parallel - when non-chunked, the improvement was not great (I...

I have tested the query optimisation (using proposed "naive" approach in webonyx/graphql-php#674) (I accidentaly posted a comment there, but it was not related to webonyx/graphql-php so I rather deleted it)....

Hi, we have an update. We've been using both chunked-broadcasting and query-caching to improve performance dramatically, but still, Lighthouse was sending (chunked, in parallel) an event (from cache) to every...

I actually think both of these approaches are valid: 1) current approach is valid for scenario like subscription for new notifications - you cannot use "rooms" because every user should...

`@shared` sounds right. When I was thinking about that directive, I think the most common scenarios would be I want to place the directive on the subscription so something like...

I see. This looks more complex and robust. Can you please provide a use case for this, I mean, when you would need this behaviour? I'm thinking that in the...

Wait a sec, this is not a good example. In your case even if the `socialSecurityNumber` is not @shared field, it still is exposed to EVERYONE. The only difference is...