From f7c745bf820177592f123490d31b293311b4f605 Mon Sep 17 00:00:00 2001 From: Greg Richardson Date: Wed, 19 Apr 2023 09:12:04 -0600 Subject: [PATCH] docs(blog): change pg_graphql to inline code --- apps/www/_blog/2023-04-19-whats-new-in-pg-graphql-v1-2.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/www/_blog/2023-04-19-whats-new-in-pg-graphql-v1-2.mdx b/apps/www/_blog/2023-04-19-whats-new-in-pg-graphql-v1-2.mdx index 9e4159cb97a..aadb5a1f194 100644 --- a/apps/www/_blog/2023-04-19-whats-new-in-pg-graphql-v1-2.mdx +++ b/apps/www/_blog/2023-04-19-whats-new-in-pg-graphql-v1-2.mdx @@ -79,7 +79,7 @@ Filtering in SQL is endlessly flexible. We’ve taken two incremental steps to b ### `is null` and `is not null` Handling `null` values can be tricky in both SQL and GraphQL. However, there are similarities we can take advantage of. -In pg_graphql, every scalar data type has its own filter type, such as `IntFilter` and `StringFilter`. +In `pg_graphql`, every scalar data type has its own filter type, such as `IntFilter` and `StringFilter`. Each of these filter types now includes an `is` argument, which allows you to filter based on whether a value is null or not null. You can do this by using `{is: NULL}` for `null` values and `{is: NOT_NULL}` for non-`null` values.