feat: Initial Supabase Functions/Triggers implementation #4844
+114
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a foundational implementation for managing PostgreSQL functions and triggers using Drizzle ORM in a Supabase environment. It provides a type-safe, declarative API to define database functions and their associated triggers.
Details:
Added
PgFunction
class and factory with support for:PostgreSQL function properties such as return type, language, behavior, security, search path, and SQL body.
Added
PgTrigger
class and factory supporting:Trigger configuration on tables, including multiple events, trigger type, orientation (row/statement), and linked function execution.
Example: