From ca2c43c741485e58ebdd49464817be609ec08577 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ramiro=20Nu=C3=B1ez=20Dosio?= Date: Fri, 21 Apr 2023 13:12:31 +0100 Subject: [PATCH] Update content Add banners with new posts Add ## More pg_graphql --- .../2022-03-29-graphql-now-available.mdx | 27 ++++++++++++++----- 1 file changed, 21 insertions(+), 6 deletions(-) diff --git a/apps/www/_blog/2022-03-29-graphql-now-available.mdx b/apps/www/_blog/2022-03-29-graphql-now-available.mdx index 15baea38dfc..72059a88c1e 100644 --- a/apps/www/_blog/2022-03-29-graphql-now-available.mdx +++ b/apps/www/_blog/2022-03-29-graphql-now-available.mdx @@ -1,6 +1,6 @@ --- title: 'GraphQL is now available in Supabase' -description: GraphQL support is now in general availability on the Supabase platform via our open source PostgreSQL extension, pg_graphql (beta). +description: GraphQL support is now in general availability on the Supabase platform via our open source PostgreSQL extension, pg_graphql. author: oli_rice,dthyresson image: launch-week-4/tuesday-graphql/graphql-thumb-og.png thumb: launch-week-4/tuesday-graphql/graphql-thumb.png @@ -11,8 +11,16 @@ date: '2022-03-29' toc_depth: 3 --- -GraphQL support is now in general availability on the Supabase platform via our [open source](https://github.com/supabase/pg_graphql/) PostgreSQL extension, -[`pg_graphql](https://supabase.github.io/pg_graphql/) (beta)`. +
+ +🆕 `pg_graphql` has undergone significant enhancements since this announcement. Here is what is new: + + - [pg_graphql v1.0](https://supabase.com/blog/pg-graphql-v1) + - [New Features in pg_graphql v1.2](https://supabase.com/blog/whats-new-in-pg-graphql-v1-2) + +
+ +GraphQL support is now in general availability on the Supabase platform via our [open source](https://github.com/supabase/pg_graphql/) PostgreSQL extension, [`pg_graphql](https://supabase.github.io/pg_graphql/) (beta)`. ![supameme.png](/images/blog/launch-week-4/tuesday-graphql/supameme.png) @@ -119,8 +127,7 @@ An advantage to embedding GraphQL directly in the database is that we can lean o ### Authentication -The GraphQL types exposed by `pg_graphql` are filtered according to the SQL role's [INSERT/UPDATE/DELETE permissions](https://www.postgresql.org/docs/current/sql-grant.html). -At Supabase, each API request is resolved in the database using the role in the request's JWT. +The GraphQL types exposed by `pg_graphql` are filtered according to the SQL role's [INSERT/UPDATE/DELETE permissions](https://www.postgresql.org/docs/current/sql-grant.html). At Supabase, each API request is resolved in the database using the role in the request's JWT. Anonymous users receive the `anon` role, and logged in users get the `authenticated` role. In either case, pg_graphql resolves requests according to the SQL permissions. The [introspection schema](https://graphql.org/learn/introspection/) is similarly filtered to limit exposed types and fields to those that the user has permission to access. @@ -134,6 +141,7 @@ Another nice side effect of making PostgreSQL do the heavy lifting is that Graph ## Performance Each [free tier database](https://supabase.com/pricing) on the Supabase platform runs on a dedicated AWS t4g.micro instance with 2 vCPUs and 1 GB of memory. + To squeeze the most out of that limited hardware we had to make a few significant optimizations: **GraphQL queries are always transpiled into exactly one SQL query** @@ -221,7 +229,7 @@ As a result of these optimizations, the throughput of a “hello world” equiva -To enable GraphQL in your Supabase instance, enable `pg_graphql` from the dashboard. +To enable GraphQL in your Supabase instance, enable `pg_graphql` from the [dashboard](https://app.supabase.com/).