From b5794eeee0a61b3eb900b6fe2accfa45d4dad67d Mon Sep 17 00:00:00 2001 From: Andrew Smith Date: Mon, 5 Sep 2022 16:31:19 +0000 Subject: [PATCH] Remove creating email function from guide --- apps/reference/docs/learn/auth-deep-dive/policies.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/apps/reference/docs/learn/auth-deep-dive/policies.md b/apps/reference/docs/learn/auth-deep-dive/policies.md index e9b10a1cb57..7533479c97c 100644 --- a/apps/reference/docs/learn/auth-deep-dive/policies.md +++ b/apps/reference/docs/learn/auth-deep-dive/policies.md @@ -138,10 +138,6 @@ There are some more notes here on how to structure your schema to best integrate Once you get the hang of policies you can start to get a little bit fancy. Let's say I work at Blizzard and I only want Blizzard staff members to be able to update people's high scores, I can write something like: ```sql -create or replace function auth.email() returns text as $$ - select nullif(current_setting('request.jwt.claims', true)::json->>'email', '')::text; -$$ language sql; - create policy "Only Blizzard staff can update leaderboard" on my_scores for update using (