mirror of
https://github.com/supabase/supabase.git
synced 2026-09-22 13:37:53 +08:00
d87904961e
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES/NO ## What kind of change does this PR introduce? Docs update ## What is the current behavior? Many troubleshooting guides referencing Postgres functions were placed in the edge function category ## What is the new behavior? Removed the "function" topic filter for guides that are unrelated to edge functions
19 lines
798 B
Plaintext
19 lines
798 B
Plaintext
---
|
|
title = "NEW variable is null in a trigger function."
|
|
github_url = "https://github.com/orgs/supabase/discussions/15934"
|
|
date_created = "2023-07-20T19:05:52+00:00"
|
|
topics = [ "database" ]
|
|
keywords = [ "trigger", "function", "statement", "row", "NEW", "OLD", "SQL" ]
|
|
database_id = "f5cabb97-aae3-4fb5-b597-4e7857821753"
|
|
---
|
|
|
|
When you create a function and call it from a trigger the NEW variable is only passed in if the trigger is on ROW operations
|
|
|
|
The UI currently defaults to STATEMENT which will not provide NEW or OLD variables to the function.
|
|
|
|

|
|
|
|
Also in SQL (reference: https://www.postgresql.org/docs/current/sql-createtrigger.html)
|
|
|
|

|