postgrest VS supabase

This is especially helpful because Supabase uses PostegREST under the hood, which does not support OpenAPI 3.x. Note that some Postgres specific features like enums are not converted to JSON Schema enums as Sequelize doesn't expose that information.

PostgREST stands out as the leading solution for PostgreSQL databases. It turns your database directly into a RESTful API with minimal configuration. The tool automatically creates endpoints for tables and views, supports complex filters, and leverages PostgreSQL's row-level security for fine-grained access control. If you'd like to see this in action, check out our Neon PostgresQL sample.

PostgREST

> I don't really see how the validation schema and ORM model would ever really diverge...

If that were the case, then using a PostgreSQL API[0] that maps tables to APIs would be all that's required.

However, the real world is messy. Requirements change, which could lead the project becoming a reimplementation of full framework such as Django.

Django also comes with generic REST endpoints based on models thus giving you the magic, but still allows for all the different use cases and customizations that might present themselves during the full lifecycle of a project.

[0]https://github.com/PostgREST/postgrest

PostgREST 12.2 is out! It comes with Observability and API improvements. In this post, we'll see what's new.

Supabase provides a RESTful API using PostgREST. However, without RLS, you will expose your database to the frontend. With the RLS policies created above, it’s safe to expose the API to the public because each user can only access the data allowed by the policy. For example, if you try to get all the List items using the API below, you will only receive the ones you are allowed to read by the read policy:

I spoke at Swiss PgDay in Switzerland in late June. The talk was about how to create a no-code API with the famous PostgreSQL database, the related PostgREST, and Apache APISIX, of course. I already wrote about the idea in a previous post. However, I wanted to improve it, if only slightly.

Supabase was started as a thin deployment layer on top of PostgreSQL and PostgREST, which implies that understanding Supabase requires understanding PostgREST and PostgreSQL.

Yes, sorry about that. We're looking at it on https://github.com/PostgREST/postgrest/issues/3503.

Yes, the Supabase description could be not easy to understand. It's become much more clear when you start using it. Let's say it that way, as Vercel is for hosting the frontend, Supabase will handle your backend. Small Postgresql database, edge functions, also auth to your app, s3-like storage, etc.

-- 1. Create a table for public profiles create table profiles ( id uuid references auth.users on delete cascade not null primary key, updated_at timestamp with time zone, full_name text, avatar_url text, -- Add other profile fields as needed constraint "profiles_id_fkey" foreign key ("id") references "auth"."users"("id") on delete cascade ); -- 2. Set up Row Level Security (RLS) -- See https://supabase.com/docs/guides/auth/row-level-security alter table profiles enable row level security; -- 3. Allow public read access for profiles create policy "Public profiles are viewable by everyone." on profiles for select using (true); -- 4. Allow individual user update access to their own profile create policy "Users can update own profile." on profiles for update using (auth.uid() = id); -- 5. Function to handle new user creation -- This function runs when a user is added to auth.users and inserts -- a corresponding row into public.profiles, extracting name/avatar if available. create or replace function public.handle_new_user() returns trigger language plpgsql security definer set search_path = public as $$ begin insert into public.profiles (id, full_name, avatar_url) values ( new.id, new.raw_user_meta_data->>'full_name', new.raw_user_meta_data->>'avatar_url' ); return new; end; $$; -- 6. Trigger to call the function after a new user is inserted create trigger on_auth_user_created after insert on auth.users for each row execute procedure public.handle_new_user();

We intend to release more Supabase UI Library components, and we'd love to get your feedback. Got a favorite component you want for your applications? Let us know on X or Discord, or we'd be happy to get a pull request.

Text embeddings are numerical vectors representing concepts like text, enabling AI tasks such as semantic search, recommendations, and clustering. This post guides you through generating text embeddings using Google Gemini via the Vercel AI SDK and storing them in a Supabase Postgres database with the pgvector extension.

Skip the complexity of Firebase and Supabase—sync your PostgreSQL data in real-time with ElectricSQL.

Create a Supabase Account – Sign up at supabase.com and start a new project.

For the backend, we will use Supabase for our database and authentication. Create a new project in Supabase and get your public Anonymous token. This token will be essential for connecting your app to the database.