Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

DOCS UPDATE: Insert Table Instructions on supabase

Open
  • Is something wrong?
#285 1 comment 0 reactions 0 assignees View on GitHub

@shrav784 is already working on this.

Since Mar 26, 2026.

  • #309 by @shrav784 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
sql, supabase
Domain
database, documentation

Research direction

Start with the Supabase setup instructions referenced in the issue and check how schema creation and initial data seeding are currently documented. Add the public.users schema and seed data there, then verify that repeated setup runs avoid duplicate usernames and that the documented setup prevents relation-not-found errors.

Written by the indexing model from the issue text.

Description

Is this related to an existing part of the documentation?
  • Yes, it is related to an existing section
What needs to be updated?

📌 Current Documentation Issue

The database schema and initial data seeding scripts are missing from the documentation, leading to "relation does not exist" errors during initial setup.

✨ Proposed Changes

Add the following SQL schema definition and seed data to the setup instructions to ensure all tables and relationships are correctly established before data insertion :
`-- Create Tables (Schema)
CREATE TABLE public.users (
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
username TEXT UNIQUE NOT NULL,
email TEXT UNIQUE NOT NULL,
role TEXT,
profile_image TEXT,
bio TEXT,
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
);

-- Seed Initial Data
INSERT INTO public.users (username, email, role, bio)
VALUES
('creator1', '[email protected]', 'creator', 'Bio of creator1'),
('brand1', '[email protected]', 'brand', 'Bio of brand1')
ON CONFLICT (username) DO NOTHING;`

📋 Additional Context

Ensuring that the users table is created in the public schema is critical for preventing 42P01 errors. The use of ON CONFLICT prevents duplicate key violations during repeated setup runs.

Relevant Documentation Link (if any)

No response

Record
  • I agree to follow this project's Code of Conduct
  • I want to work on this update
Dominant language
TypeScript
Stars
101
Forks
145
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AOSSIE-Org/InPactAI

All issues in AOSSIE-Org/InPactAI

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.