From d1f7333ccafce270a388283a691f46a68c1be438 Mon Sep 17 00:00:00 2001 From: Richard Hyesung O Date: Sat, 22 Apr 2023 11:04:53 -0400 Subject: [PATCH 1/4] Add note for Pro projects to contact support to upgrade --- .../pages/guides/platform/migrating-and-upgrading-projects.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx b/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx index 0586ea2c09c..57a8b9321a9 100644 --- a/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx +++ b/apps/docs/pages/guides/platform/migrating-and-upgrading-projects.mdx @@ -12,7 +12,7 @@ In some cases, access to new features require upgrading or migrating your Supaba ## Upgrade your project -This is only available for projects on the Free plan. +This is only available for projects on the Free plan. For projects on the Pro plan, please contact support for assistance with upgrading. When you pause and restore a project, the restored database includes the latest features. This method _does_ include downtime, so be aware that your project will be inaccessible for a short period of time. From 3ea3b9885f5fca84ef8824aa1d585ebb21e92002 Mon Sep 17 00:00:00 2001 From: Richard Hyesung O Date: Sat, 22 Apr 2023 11:12:01 -0400 Subject: [PATCH 2/4] Add note to users to upgrade to v1.2, with docs link --- .../2023-04-21-whats-new-in-pg-graphql-v1-2.mdx | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx b/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx index 539350f8c87..b0b83f31716 100644 --- a/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx +++ b/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx @@ -15,10 +15,12 @@ thumb: launch-week-6/pggraphql/og-pg-graphql.png --- It's been 4 months since the [1.0.0 release of pg_graphql](https://supabase.com/blog/pg-graphql-v1). -Since then, we’ve pushed several features to improve the APIs that `pg_graphql` produces. +Since then, we’ve pushed several features to improve the APIs that `pg_graphql` produces. In this article, we’ll walk through those features and show examples of each. +These features are only available after upgrading your project to v1.2.0. For help with upgrading, please review the documentation [here](https://supabase.com/docs/guides/platform/migrating-and-upgrading-projects). + ### View Support Prior to `v1.1`, `pg_graphql` would only reflect standard tables. Since then, views, materialized views, and foreign tables are now also reflected in the GraphQL schema. @@ -26,7 +28,7 @@ Prior to `v1.1`, `pg_graphql` would only reflect standard tables. Since then, vi For example: ```sql -create view "ProjectOwner" as +create view "ProjectOwner" as select acc.id, acc.name @@ -70,7 +72,7 @@ With associated `Edge` and `Connection` types. That enables querying via: } ``` -Additionally, simple views automatically support mutation events like inserts and updates. You might use these to migrate underlying tables while maintaining backwards compatibility with previous API versions. +Additionally, simple views automatically support mutation events like inserts and updates. You might use these to migrate underlying tables while maintaining backwards compatibility with previous API versions. ## Filtering @@ -109,7 +111,7 @@ to return all `blog`s where the `name` is `null`. ### **`like`**, **`ilike`**, and **`startsWith`** -Text filtering options in `pg_graphql` have historically been restricted to equality checks. The hesitation was due to concerns about exposing a default filter that is difficult to index. The combination of [citext](https://www.postgresql.org/docs/current/citext.html) and [PGroonga available on the platform](https://supabase.com/docs/guides/database/extensions/pgroonga) solves those scalability risks and enabled us to expand the `StringFilter` with options for `like` `ilike` and `startsWith`. +Text filtering options in `pg_graphql` have historically been restricted to equality checks. The hesitation was due to concerns about exposing a default filter that is difficult to index. The combination of [citext](https://www.postgresql.org/docs/current/citext.html) and [PGroonga available on the platform](https://supabase.com/docs/guides/database/extensions/pgroonga) solves those scalability risks and enabled us to expand the `StringFilter` with options for `like` `ilike` and `startsWith`. ```graphql input StringFilter { @@ -118,7 +120,7 @@ input StringFilter { startsWith: String like: String ilike: String -} +} ``` Note that `startsWith` filters should be preferred where appropriate because they can leverage simple B-Tree indexes to improve performance. @@ -139,7 +141,7 @@ Note that `startsWith` filters should be preferred where appropriate because the ### GraphQL directives `@skip` and `@include` -The GraphQL spec has evolved over time. Although the spec is clear, it is common for GraphQL servers to selectively omit some chunks of functionality. For example, some frameworks intentionally do not expose an introspection schema as a form of security through obscurity. +The GraphQL spec has evolved over time. Although the spec is clear, it is common for GraphQL servers to selectively omit some chunks of functionality. For example, some frameworks intentionally do not expose an introspection schema as a form of security through obscurity. `pg_graphql` aims to be unopinionated and adhere exactly to the spec. The `@skip` and `@include` directives are part of the [GraphQL core specification](https://spec.graphql.org/October2021/#sec--skip) and are now functional. @@ -198,6 +200,6 @@ The headline features we aim to launch in coming releases of `pg_graphql` includ ## More pg_graphql -- [Introducing pg_graphql: A GraphQL extension for PostgreSQL](https://supabase.com/blog/pg-graphql) +- [Introducing pg_graphql: A GraphQL extension for PostgreSQL](https://supabase.com/blog/pg-graphql) - [GraphQL is now available in Supabase](https://supabase.com/blog/graphql-now-available) - [pg_graphql v1.0](https://supabase.com/blog/pg-graphql-v1) From 292edafec6c36e3bb300b89d8191914a2d8bb35b Mon Sep 17 00:00:00 2001 From: Richard Hyesung O Date: Sun, 23 Apr 2023 00:19:55 -0400 Subject: [PATCH 3/4] Remove unavailable Admonition component, replace with div --- apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx b/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx index b0b83f31716..905fbfe3190 100644 --- a/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx +++ b/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx @@ -19,7 +19,11 @@ Since then, we’ve pushed several features to improve the APIs that `pg_graphql In this article, we’ll walk through those features and show examples of each. -These features are only available after upgrading your project to v1.2.0. For help with upgrading, please review the documentation [here](https://supabase.com/docs/guides/platform/migrating-and-upgrading-projects). +
+ +📢 These features are only available after upgrading your project to v1.2.0. For help with upgrading, please review the documentation [here](https://supabase.com/docs/guides/platform/migrating-and-upgrading-projects). + +
### View Support From 3dc8845f5d40a20887b5aff717f5986c16d0829f Mon Sep 17 00:00:00 2001 From: Greg Richardson Date: Mon, 24 Apr 2023 13:59:19 -0600 Subject: [PATCH 4/4] docs(pg_graphql): mention pg version 15.1.0.63 --- apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx b/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx index 905fbfe3190..d3cd7fb012c 100644 --- a/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx +++ b/apps/www/_blog/2023-04-21-whats-new-in-pg-graphql-v1-2.mdx @@ -21,7 +21,7 @@ In this article, we’ll walk through those features and show examples of each.
-📢 These features are only available after upgrading your project to v1.2.0. For help with upgrading, please review the documentation [here](https://supabase.com/docs/guides/platform/migrating-and-upgrading-projects). +📢 These features are only available on projects with Postgres version `15.1.0.63` or higher. For help with upgrading, please review the [migrating and upgrading projects guide](https://supabase.com/docs/guides/platform/migrating-and-upgrading-projects).