hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2025-01-05 22:34:22 +03:00
Code Issues Projects Releases Wiki Activity

fix: correct typo in 'Idea #2' section (close#2513) (#2514)

Browse Source 
This change fixes a typo found on line 95 where the word 'wow' had been used instead of 'now'
This commit is contained in:
Michael Edelman 2019-07-12 02:37:31 -04:00 committed by Shahidh K Muhammed
parent 694ba2cb6d
commit 6baf0b9ed0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
architecture/live-queries.md
View File

@ -92,7 +92,7 @@ Incidentally, because we had started the engineering work behind Hasura many yea
Because of implementing authorization at the application layer in Hasura (instead of using RLS and passing user-details via current session settings in the postgres connection) had significant benefits, which we’ll soon see.
To summarise, wow that authorization is declarative and available at a table, view or even a function (if the function returns SETOF) it is possible to create a single SQL query that has the authorization rules.
To summarise, now that authorization is declarative and available at a table, view or even a function (if the function returns SETOF) it is possible to create a single SQL query that has the authorization rules.
GraphQL query → GraphQL AST → Internal AST with authorization rules → SQL AST → SQL