RetailCRM-Mirror/graphql-php
1
0
Fork 0
mirror of https://github.com/retailcrm/graphql-php.git synced 2024-11-26 14:56:03 +03:00
Code Issues Projects Releases Wiki Activity

Added "since" entry to docs for N+1 problem and async support

Browse Source
This commit is contained in:
vladar 2016-12-14 20:22:38 +07:00
parent 8e39b3d88d
commit c7688c9249
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/data-fetching.md
View File

@ -152,6 +152,8 @@ Keep in mind that **field resolver** has precedence over **default field resolve
# Solving N+1 Problem # Solving N+1 Problem
Since: 9.0
One of the most annoying problems with data fetching is so-called [N+1 problem](https://secure.phabricator.com/book/phabcontrib/article/n_plus_one/). One of the most annoying problems with data fetching is so-called [N+1 problem](https://secure.phabricator.com/book/phabcontrib/article/n_plus_one/).
Consider following GraphQL query: Consider following GraphQL query:
@ -217,6 +219,8 @@ In this example only one query will be executed for all story authors comparing
in naive implementation. in naive implementation.
# Async PHP # Async PHP
Since: 9.0
If your project runs in environment that supports async operations If your project runs in environment that supports async operations
(like `HHVM`, `ReactPHP`, `Icicle.io`, `appserver.io` `PHP threads`, etc) you can leverage (like `HHVM`, `ReactPHP`, `Icicle.io`, `appserver.io` `PHP threads`, etc) you can leverage
the power of your platform to resolve fields asynchronously. the power of your platform to resolve fields asynchronously.