Skip to content

[FEAT] : Canonical Schema Syntax Error #3130

Closed

Description

@hrshjswniii

Problem Statement

The canonical database schema definition file supabase/schema.sql is used to bootstrap the database tables, indices, and row-level security (RLS) policies for new developers setting up DevTrack locally.

However, there is a syntax error at line 300 of this file, where a duplicate closing parenthesis and semicolon ); exist immediately following the leaderboard_cache table creation statement:

292: CREATE TABLE IF NOT EXISTS leaderboard_cache (
293:   key text primary key,
...
298:   updated_at timestamptz default now()
299: );
300: ); -- <-- Stray syntax block causing execution failure

This syntax error causes new database initialization scripts, local Supabase CLI runs, or docker-compose setups to crash during database bootstrapping, frustrating new open-source contributors.

Proposed Solution

Clean up the syntax drift in the schema setup file:

  1. Open the file supabase/schema.sql.
  2. Locate line 300.
  3. Remove the stray ); characters to ensure the syntax is valid PostgreSQL.

Feature Area

New Feature Area

Alternatives Considered

  • Ignoring the schema file and relying solely on incremental migrations: Rejected because incremental migrations can grow extremely large over time. Bootstrapping with a single, consolidated schema definition file is standard practice for new setups.

Acceptance Criteria

  • The stray ); on line 300 is removed from supabase/schema.sql.
  • Running schema.sql on a clean, empty PostgreSQL/Supabase database completes successfully from start to finish without any SQL parse or execution errors.

Additional Context

No response

Activity

  1. hrshjswniii commented on Jul 4, 2026

    @hrshjswniii
    ContributorAuthor

    Hiii @Priyanshu-byte-coder , i'd like to work on this issue as part of GSSoC'26

  2. github-actions commented on Jul 4, 2026

    @github-actions

    Assigned to @hrshjswniii! You have 7 days to open a PR. No PR after 7 days = auto-unassigned so others can pick it up. Good luck!

  3. radhikatbbt commented on Jul 6, 2026

    @radhikatbbt

    /assign

  4. github-actions commented on Jul 12, 2026

    @github-actions

    ✅ Closed as completed!

    If DevTrack has been useful, a ⭐ star on the repo helps the project grow and reach more developers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions