feat: designed and implemented database schema and tables by Berny-ft · Pull Request #38 · hack4impact/mcld-project

Berny-ft · 2026-04-01T02:19:46Z

Closes #4

Overview

Designed and implemented the PostgreSQL database schema for the MCLD platform using Drizzle ORM. Created tables for profiles, services, schedules, service bookings, webinars, webinar registrations, and coaching sessions. Also added Stripe payment infrastructure (subscriptions, purchases tables, webhook handler, and Stripe sync helpers) to support the upcoming payment feature.

Testing

Manually pushed the schema to Supabase using pnpm db:push and verified all tables appear in the Supabase dashboard under the database section.
Screenshots / Screencasts
N/A — no frontend changes in this PR.

Checklist
[x] Code is neat, readable, and works
[x] Code is commented where appropriate and well-documented
[x] Commit messages follow our guidelines
[x] Issue number is linked
[x] Branch is linked
[x] Reviewers are assigned (one of your tech leads)

Notes

Coach availability was intentionally excluded from this schema — coaches do not set recurring availability in this version of the platform. This decision is reflected in the docs.

martin0024

Please before reviewing the PR remove any code snippets related to stripe. This PR should only include db schema. Thanks!

Copilot

Pull request overview

Designs and documents an initial PostgreSQL schema for the MCLD platform using Drizzle ORM, along with dependency updates.

Changes:

Expanded lib/db/schema.ts with enums and tables for profiles, services/schedules/bookings, webinars/registrations, coaching sessions, and Stripe-related tables.
Added Mermaid ERD documentation under docs/ (plus a broader stack explainer).
Added an initial Drizzle SQL migration and updated Drizzle/other dependencies.

Reviewed changes

Copilot reviewed 8 out of 9 changed files in this pull request and generated 11 comments.

Show a summary per file

File	Description
pnpm-lock.yaml	Locks updated dependency versions (Supabase, Drizzle, lint tooling, etc.).
package.json	Bumps `drizzle-orm` version.
lib/db/schema.ts	Defines the intended Drizzle schema (enums + tables incl. Stripe tables).
drizzle/0000_thick_nemesis.sql	Adds a SQL migration (currently inconsistent with `schema.ts`).
drizzle.config.ts	Adds `schemaFilter: ["public"]` configuration.
docs/schema-overview.md	Mermaid overview ERD for the intended schema.
docs/profiles.md	Profiles table documentation.
docs/services.md	Services/schedules/bookings documentation.
docs/webinars.md	Webinars/registrations documentation.
docs/coaching.md	Coaching sessions documentation.
docs/stack-explainer.md	Broad project stack reference.

Files not reviewed (1)

pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-04-01T12:05:33Z

+export const roleEnum = pgEnum("role", ["user", "admin", "coach"]);
+export const serviceTypeEnum = pgEnum('service_type', ["coaching_session", "booking"]);
+export const bookingStatusEnum = pgEnum('booking_status', ["pending", "confirmed", "cancelled"]);
+export const webinarTierEnum = pgEnum('webinar_tier', ["free", "premium"]);


The PR description mentions service types “preset date” and “user-scheduling”, but the newly introduced service_type enum here is coaching_session vs booking. Either update the PR description (and any docs) to reflect the new meaning, or rename/adjust the enum values to match the originally described service-type model.

Copilot · 2026-04-01T12:05:33Z

+export const subscriptions = pgTable("subscriptions", {
+   id: uuid("id").primaryKey().defaultRandom(),
+   userId: uuid("user_id").references(() => profiles.id, { onDelete: "cascade" }).notNull().unique(),
+   stripeSubscriptionId: text("stripe_subscription_id").unique(),
+   status: text("status").notNull().default("none"),
+   stripePriceId: text("stripe_price_id"),
+   cancelAtPeriodEnd: boolean("cancel_at_period_end").notNull().default(false),
+   paymentMethodBrand: text("payment_method_brand"),
+   paymentMethodLast4: text("payment_method_last4"),
+   createdAt: timestamp("created_at").defaultNow().notNull(),
+   updatedAt: timestamp("updated_at").defaultNow().notNull(),
+});
+
+export const purchases = pgTable("purchases", {
+   id: uuid("id").primaryKey().defaultRandom(),
+   userId: uuid("user_id").references(() => profiles.id, { onDelete: "cascade" }).notNull(),
+   stripePriceId: text("stripe_price_id").notNull(),
+   stripeSessionId: text("stripe_session_id").notNull().unique(),
+   productName: text("product_name").notNull(),
+   amount: integer("amount").notNull(),
+   currency: text("currency").notNull(),
+   createdAt: timestamp("created_at").defaultNow().notNull(),
 });


The PR description claims a Stripe webhook handler and Stripe sync helpers were added, but the PR changes only add schema tables (no webhook route handler or helper modules are present in the codebase). Either include the webhook/sync code in this PR, or update the PR description to accurately reflect what’s actually being shipped.

Copilot · 2026-04-01T12:05:33Z

@@ -0,0 +1,20 @@
+# Profiles Table
+
+Mirrors Supabase `auth.users` — populated via a database trigger on signup. Stores display data and the user's role within the platform.


This doc states the profiles table is populated via a database trigger on signup, but there is no trigger defined in the committed Drizzle migration(s). Unless triggers are managed elsewhere (e.g., Supabase UI), this is inaccurate; either add the trigger to migrations or revise the documentation to reflect the actual population mechanism.

Suggested change

Mirrors Supabase `auth.users` — populated via a database trigger on signup. Stores display data and the user's role within the platform.

Mirrors Supabase `auth.users`. Stores display data and the user's role within the platform.

Copilot · 2026-04-01T12:05:34Z

+## Services
+
+The central catalog of offerings on the platform. Two types:
+- **`booking`** — a bookable service; has an associated `schedules` row (via `scheduling_id`).
+- **`coaching_session`** — a coaching offering; `scheduling_id` is null — the scheduling is handled through the `coaching_sessions` table.
+


The relationship description here says booking services “have an associated schedules row (via scheduling_id)”, but the schema links schedules to services via schedules.service_id and does not enforce services.scheduling_id as a foreign key. Update the docs (or the schema) so the described relationship matches the actual constraints and intended source of truth.

Berny-ft · 2026-04-01T12:09:30Z

Please before reviewing the PR remove any code snippets related to stripe. This PR should only include db schema. Thanks!

Done, plz check again. Thx!

martin0024 · 2026-04-01T16:54:48Z

+    webinar_registrations {
+        uuid id PK
+        uuid user_id FK


This shouldn't exist since the flow is either :

free to watch webinars

subscribers only webinars

They don't need to register, it's like youtube videos.
Please update the schema as well as the documentation.

martin0024 · 2026-04-01T16:57:27Z

+
+```mermaid
+erDiagram
+    services {


please add updatedAt on the flow, since services can be modified/edited.

martin0024 · 2026-04-01T17:01:54Z

@RenaudBernier does the coach sessions flow works for you ? Good work Berny

RenaudBernier

Looks good overall, just some variable name changes and the time slots. good job overall, i'm sure that everything will be perfect after your changes

RenaudBernier · 2026-04-01T20:23:09Z

+        session_status status "pending | confirmed | cancelled | completed"
+        text meeting_url
+        text notes
+        time[] selected_time_slots


We need a way to store timeslots of different lengths. The user might for example select April 14th 2-5pm and April 17th 10am-3pm. time[] is just an array of timestamps, it can't store timeslots. Please work on finding a solution to this. Should we use a certain string format? Maybe some better solution?

RenaudBernier · 2026-04-01T20:26:47Z

+    schedules {
+        uuid id PK
+        uuid service_id FK
+        jsonb data
+        timestamp created_at
+    }


I don't understand this table, just explain it to me here please

When a service is of type “booking,” it has a linked row in the schedules table and accepts a JSON blob containing data about the format, such as specific time slots within a given period. I'll rename the table to maybe something that is easier to understand

RenaudBernier · 2026-04-01T20:27:54Z

+    webinars {
+        uuid id PK
+        text title
+        text description
+        webinar_tier tier
+        int duration_minutes
+        text meeting_url
+        boolean is_active
+        timestamp created_at
+    }


Webinars aren't meetings, they're recordings on youtube. change meeting_url to youtube_url please

RenaudBernier · 2026-04-01T20:28:52Z

+    coaching_sessions {
+        uuid id PK
+        uuid service_id FK
+        uuid coach_id FK
+        uuid user_id FK
+        timestamp scheduled_at
+        int duration_minutes
+        session_status status
+        text meeting_url
+        text notes
+        time[] selected_time_slots
+        timestamp created_at
+    }


Same as my comment in the .md, please review how we will store timeslots

…o log time for services of type coaching

RenaudBernier

Thanks for the changes, Berny. lgtm

Berny-ft added 8 commits March 28, 2026 15:02

docs

df87ca6

schema

097b709

added missing column in docs

ed1a032

pnpm setup

da1742a

fixed services

24f9702

fixed webinars

07e6de7

removed seats from webinars

73ff387

updated docs

4d93dbd

Copilot AI review requested due to automatic review settings April 1, 2026 02:19

RenaudBernier requested review from achneerov and martin0024 and removed request for Copilot April 1, 2026 02:35

martin0024 requested a review from Copilot April 1, 2026 02:35

RenaudBernier review requested due to automatic review settings April 1, 2026 02:35

Copilot started reviewing on behalf of martin0024 April 1, 2026 02:35 View session

Berny-ft closed this Apr 1, 2026

Berny-ft reopened this Apr 1, 2026

Berny-ft changed the base branch from main to dev April 1, 2026 02:40

martin0024 requested changes Apr 1, 2026

View reviewed changes

feat: updated schema to have subscriptions and purchases

7ba83a7

Berny-ft force-pushed the feature/4-db-schema branch from a9342d9 to 7ba83a7 Compare April 1, 2026 12:01

Copilot AI review requested due to automatic review settings April 1, 2026 12:01

Copilot started reviewing on behalf of Berny-ft April 1, 2026 12:01 View session

Berny-ft changed the title ~~Feature/4 db schema~~ Feat : Designed and implemented database schema and tables Apr 1, 2026

removed unused files

ba9a262

Copilot AI reviewed Apr 1, 2026

View reviewed changes

martin0024 requested changes Apr 1, 2026

View reviewed changes

RenaudBernier requested changes Apr 1, 2026

View reviewed changes

Berny-ft added 2 commits April 1, 2026 17:53

fixed schedule table, timeslots, youtube_url and update times

f57b223

removed the schedules table , added a scheduled at blob to services t…

9f607ff

…o log time for services of type coaching

RenaudBernier approved these changes Apr 1, 2026

View reviewed changes

Berny-ft merged commit b606166 into dev Apr 2, 2026

khoa-l changed the title ~~Feat : Designed and implemented database schema and tables~~ feat: designed and implemented database schema and tables Apr 7, 2026

martin0024 deleted the feature/4-db-schema branch April 14, 2026 22:53

		@@ -0,0 +1,20 @@
		# Profiles Table

		Mirrors Supabase `auth.users` — populated via a database trigger on signup. Stores display data and the user's role within the platform.

	Mirrors Supabase `auth.users` — populated via a database trigger on signup. Stores display data and the user's role within the platform.
	Mirrors Supabase `auth.users`. Stores display data and the user's role within the platform.

Conversation

Berny-ft commented Apr 1, 2026 • edited by khoa-l Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

Testing

Notes

Uh oh!

martin0024 left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

Berny-ft commented Apr 1, 2026

Uh oh!

martin0024 Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

martin0024 Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

martin0024 commented Apr 1, 2026

Uh oh!

RenaudBernier left a comment

Choose a reason for hiding this comment

Uh oh!

RenaudBernier Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

RenaudBernier Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

Berny-ft Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

RenaudBernier Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

RenaudBernier Apr 1, 2026

Choose a reason for hiding this comment

Uh oh!

RenaudBernier left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Berny-ft commented Apr 1, 2026 •

edited by khoa-l

Loading

RenaudBernier left a comment •

edited

Loading