docs: replace pgpolicy with crudpolicy #2499
Conversation
|
@dhanushreddy291 is attempting to deploy a commit to the neondatabase Team on Vercel. A member of the Team first needs to authorize it. |
| @@ -257,51 +263,50 @@ export async function TodoList() { | |||
| ```typescript shouldWrap | |||
| 'use client'; | |||
|
|
|||
| import type { Todo } from '@/app/schema'; | |||
There was a problem hiding this comment.
all of these were just proper indentation changes
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| @@ -141,16 +141,18 @@ Now that you’ve integrated Auth0 with Neon Authorize, you can securely pass JW | |||
|
|
|||
| ### 1. Add Row-Level Security policies | |||
|
|
|||
| Below are examples of RLS policies for a **todos** table, designed to restrict access so that users can only create, view, update, or delete their own todos. | |||
| Here's how to implement RLS policies for a **todos** table using a `crudPolicy`. This policy ensure users can only access and modify their own todos. | |||
There was a problem hiding this comment.
Let's keep the language explaining these are examples only. We don't want people thinking they need to copy-paste these samples as part of the mandatory setup. Also, the drizzle tab is using crudPolicy, but the SQL tab is still using granular RLS.
"Here are examples of implementing RLS policies for a todos table – the Drizzle example leverages the simplified crudPolicy function, while the SQL example demonstrates the use of individual RLS policies."
|
@davidgomes can you review the change to crudPolicy for the Drizzle tabs on these quickstart pages? |
dhanushreddy291
force-pushed
the
update-docs/use-crud-policy
branch
2 times, most recently
from
b153dbb
to
8c00266
Compare
dhanushreddy291
force-pushed
the
update-docs/use-crud-policy
branch
from
8c00266
to
624fdfb
Compare
pgPolicywithcrudPolicypreview: