Predict which products
will explode next

-- Prodiqt Database Schema -- Run this entire block in Supabase SQL Editor -- 1. User profiles (auto-created on signup) create table if not exists public.profiles ( id uuid references auth.users on delete cascade primary key, full_name text, plan text default 'starter', alert_threshold int default 80, created_at timestamptz default now(), updated_at timestamptz default now() ); -- 2. User watchlist (synced per user) create table if not exists public.watchlist ( id bigserial primary key, user_id uuid references auth.users on delete cascade not null, product_id int not null, product_name text, product_emoji text, viral_score int, created_at timestamptz default now(), unique(user_id, product_id) ); -- 3. Alerts / notifications create table if not exists public.alerts ( id bigserial primary key, user_id uuid references auth.users on delete cascade not null, title text not null, body text, icon text default '🔔', product_id int, read boolean default false, created_at timestamptz default now() ); -- 4. Products cache (populated by your data pipeline) create table if not exists public.products ( id bigserial primary key, name text not null, category text, emoji text default '📦', viral_score int default 0, weekly_growth text, video_count text, creator_count int default 0, source_cost text, sell_price text, margin int default 0, alibaba_url text, tiktok_hashtag text, data_source text default 'demo', last_updated timestamptz default now() ); -- 5. Auto-create profile on user signup 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) values ( new.id, coalesce(new.raw_user_meta_data->>'full_name', split_part(new.email, '@', 1)) ) on conflict (id) do nothing; return new; end; $$; drop trigger if exists on_auth_user_created on auth.users; create trigger on_auth_user_created after insert on auth.users for each row execute procedure public.handle_new_user(); -- 6. Enable Row Level Security on all tables alter table public.profiles enable row level security; alter table public.watchlist enable row level security; alter table public.alerts enable row level security; alter table public.products enable row level security; -- 7. Policies: users can only see/edit their own data create policy "own_profile" on public.profiles for all using (auth.uid() = id) with check (auth.uid() = id); create policy "own_watchlist" on public.watchlist for all using (auth.uid() = user_id) with check (auth.uid() = user_id); create policy "own_alerts" on public.alerts for all using (auth.uid() = user_id) with check (auth.uid() = user_id); create policy "read_products" on public.products for select using (true); -- Done! Your Prodiqt database is ready.