docs: Fix incorrect RLS original word in examples (#26937)

Fix incorrect RLS original word

Co-authored-by: Charis <26616127+charislam@users.noreply.github.com>
This commit is contained in:
cylussandCharis authored and GitHub committed 2024-06-04 01:08:30 +00:00
1 parent 4e7ff2a245
commit bfa54a2ca1
11 files changed
+11 -11

No files matched your search

@@ -109,7 +109,7 @@ Users with the `moderator` role can delete all messages. Users with the `admin`
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -37,7 +37,7 @@ The `anon` key is your client-side API key. It allows "anonymous access" to your
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -28,7 +28,7 @@ The `anon` key is your client-side API key. It allows "anonymous access" to your
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -54,7 +54,7 @@ Run the application: `npm run start`. Open your browser to `https://localhost:42
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -50,7 +50,7 @@ Run the application: `npm start`.
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -64,7 +64,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:3000
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -56,7 +56,7 @@ Run the application: `npm run dev`. Open your browser to the url indicated in th
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -64,7 +64,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:5173
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -59,7 +59,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:3000
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -57,7 +57,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:5173
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.
@@ -32,7 +32,7 @@ Run the application: `npm run dev`. Open your browser to `https://localhost:5173
### Postgres Row level security
This project uses very high-level Authorization using Postgres' Role Level Security.
This project uses very high-level Authorization using Postgres' Row Level Security.
When you start a Postgres database on Supabase, we populate it with an `auth` schema, and some helper functions.
When a user logs in, they are issued a JWT with the role `authenticated` and their UUID.
We can use these details to provide fine-grained control over what each user can and cannot do.