dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-14 05:39:11 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update event-triggers.mdx

Browse Source 
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This commit is contained in:
Chris Gwilliamsandgithub-actions[bot] authored and GitHub committed 2025-08-06 08:38:09 +03:00
1 parent d043ff7607
commit 4ee7e08493
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/guides/database/postgres/event-triggers.mdx
+1 -1
View File
@@ -10,7 +10,7 @@ In Postgres, an [event trigger](https://www.postgresql.org/docs/current/event-tr
With our `Supautils` extension (installed automatically for all Supabase projects), the `postgres` user has the ability to create and manage event triggers.
Some use cases for event triggers ares:
- Capturing Data Definition Language (DDL) changes - these are changes to your database schema (though the [pgaudit](/docs/guides/database/extensions/pgaudit) extension provides a more complete solution)
- Capturing Data Definition Language (DDL) changes - these are changes to your database schema (though the [pgAudit](/docs/guides/database/extensions/pgaudit) extension provides a more complete solution)
- Monitoring/preventing actions - such as preventing tables from being dropped in Production or enforcing RLS on all new tables
In this guide, we will go through an example event trigger that prevents accidental dropping of a table