Supabase SQL
Add Constraint
Template for adding a constraint.
Add column
Template to add a column. Make sure to change the name and type.
Automatically update timestamps
Update a column timestamp on every update.
Basic Aggregrate Functions
Set of functions to perform calculation on a set of values. The return is a single summary value. (Except for "round()")
CRON job with pg_cron
Schedule PostgreSQL commands directly from the database.
Case Expression
Case Expression.
Change Column Type
Template to modify a column type. Make sure to change the name and type.
Create View
Basic view template. Change according to your preference.
Create basic table
Basic table template. Change "table_name" to the name you prefer.
Create function
Template to create a simple function.
Create function that return integer
Template to create a function that return integer like count of rows.
Create function that return table
Template to create a function a function that return set of table.
Create table with constraints
Table with constraints example.
Create table with foreign key
Table with foreign key (fk) template. Change "table_name" to the name you prefer.
Drop Constraint
Template for dropping / removing constraint.
Drop Function
Template for dropping / removing function.
Drop RLS
Template for dropping / removing row level security.
Drop Trigger
Template for dropping / removing trigger from table.
Drop View
Template for dropping / removing a view.
Full Text Search
How to use full text search in PostgreSQL.
Generate Youtube-like short ID
Generate YouTube-like short IDs as Postgres Primary Keys.
Get columns info of a table
Template to describe a table.
Handle New User - Function & Trigger
Insert new user data into another table when event new user signup using Supabase Auth.
Increment field value
Update a field with incrementing value using stored procedure.
List all constraints
List all constraints and their tables.
List all foreign keys
List all foreign keys (FKs) and their columns.
List all functions
List all the functions in (predefined/user-defined).
List all primary keys
List all primary keys (PKs) and their columns.
List all table size
List all table data size.
List all triggers
List all the triggers in (predefined/user-defined).
Query specific text from text[]
Query rows that has specific text you need in a text array.
RLS Advanced policies
Row level security with advanced/complicated policies.
RLS Edit Policy
Row level security editing.
RLS Policies with joins
Row level security that requires table joins .
RLS Policies with security definer functions
Row level security that make use of security definer functions .
RLS Read Access
Row level security for read access.
RLS Restrict updates
Row level security for restrict updates.
RLS Time to live for rows
Row level security policies to implement TTL.
RLS Verifying email domains
Row level security that verify email domains.
Rename Constraints
Template to rename any constraints you have.
Seed unlimited users
SQL seed function for table auth.users.
Sequence operations
Define a sequence generator.
Show Postgres version
Check your database version.
Stripe subscriptions
Starter template for the Next.js Stripe Subscriptions Starter.
Todo List
Build a todo list with Row Level Security.
Update Constraint
Template for updating a constraint.
World Countries
Create a Country table for every countries in the world.
Generate Youtube-like short ID
Generate YouTube-like short IDs as Postgres Primary Keys.
pg-shortkey
This installs a trigger and type which allow you to use YouTube-like short IDs (e.g. 1TNhBqYo-6Q) as Postgres Primary Keys. Just like the YouTube IDs, SHORTKEY IDs are fixed length and URL-safe.
create table test (id shortkey primary key, name text);
create trigger trigger_test_genid before insert on test for each row execute procedure shortkey_generate();
-- generate
insert into test(name) values ('bob'), ('joe');
-- user-supplied id
insert into test(id, name) values ('1tnhbqyo-6q', 'lisa');
select * from test;
-- id name
-- 4e_z0mhjvrk bob
-- wiz_j0hibuq joe
-- 1tnhbqyo-6q lisa
shortkey is compatible with text and should be handled as such by most sane ORMs. If not, create a type mapping to whatever your string type is in your app/ORM.
Caveats
SHORTKEYs are truly random, so they fragment the index space just like v4 UUIDs, decreasing performance slightly. But unlike UUID (which provides an instance-local pseudo-sequential type via UUID v1 MC), that behavior can't be changed. This is intentional. SHORTKEYs are supposed to be used for external facing IDs, like in APIs.
There, they prevent enumeration and cardinality evaluation (e.g. how many things are there and what's the next/previous thing - just like YouTube). Use where appropriate.