Skip to content

doc (examples) Clarify computed column function criteria #462

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benjie merged 2 commits into from
May 24, 2017
Merged

doc (examples) Clarify computed column function criteria #462

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
daef9b2
doc (examples) Clarify computed column function criteria
kenips May 10, 2017
94ae1fb
Merge branch 'master' into bug/example_tutorial_update
benjie May 24, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion examples/forum/TUTORIAL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -308,7 +308,7 @@ Don’t get too stuck on the function implementations. It is fairly easy to disc
>
> 1. The function has a table row as the first argument.
> 2. The function is in the same schema as the table of the first argument.
> 3. The function’s name is prefixed by the table first argument’s name.
> 3. The function’s name is prefixed by the table’s name.
> 4. The function is marked as `stable` or `immutable` which makes it a query and not a mutation.
>
> All three of the above functions meet these conditions and as such will be computed fields. In GraphQL this ends up looking like:
Expand Down