From ad6ec015cded7ea3de38b10d9ec3cfecf27f01df Mon Sep 17 00:00:00 2001
From: Ollie Halliday <22655069+Hallidayo@users.noreply.github.com>
Date: Mon, 30 May 2022 11:05:26 +0100
Subject: [PATCH] link added to follow github issue

---
 web/docs/guides/integrations/prisma.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/web/docs/guides/integrations/prisma.mdx b/web/docs/guides/integrations/prisma.mdx
index 05c78f3be8d..2e202fb2efc 100644
--- a/web/docs/guides/integrations/prisma.mdx
+++ b/web/docs/guides/integrations/prisma.mdx
@@ -119,7 +119,7 @@ This will create a `prisma/migrations` folder inside your `prisma` directory and
 
 ### Confirming Realtime Functionality
 
-There is an existing issue where Prisma will create Enum Types wrapped in double quotation marks in PostgreSQL. This is not compatible with Realtime-enabled database tables whose columns rely on those Enum Types. We are working on a fix but the workaround is to alter and rename the Enum Types. You can use the following query to find all Types with double quotation marks in the `public` schema:
+There is an existing issue where Prisma will create Enum Types wrapped in double quotation marks in PostgreSQL. This is not compatible with Realtime-enabled database tables whose columns rely on those Enum Types. We are working on a fix which can be tracked on this [GitHub issue](https://github.com/supabase/supabase/issues/5685), but the workaround is to alter and rename the Enum Types. You can use the following query to find all Types with double quotation marks in the `public` schema:
 
 ```sql
 select distinct(a.atttypid::regtype)