Database Schema

`WaitlistSignUps`

Stores waitlist registrations with built-in referral tracking and lifecycle management.

schema.prisma

model WaitlistSignUps {
  id           String            @id @default(cuid())
  email        String            @unique
 
  referralCode String            @unique
  referredById String?
  referredBy   WaitlistSignUps?  @relation("referral", fields: [referredById], references: [id], onUpdate: Cascade, onDelete: Cascade)
  referrals    WaitlistSignUps[] @relation("referral")
 
  offboardedAt DateTime?
  discardedAt  DateTime?
 
  updatedAt    DateTime          @default(now())
  createdAt    DateTime          @default(now())
 
  @@index(referralCode)
  @@index(email)
}

Field	Description
`id`	Unique identifier for each signup, auto-generated using CUID.
`email`	User's email address, must be unique across all signups.
`referralCode`	Unique code generated for this user to share with others.
`referredById`	Optional ID linking to the user who referred this signup.
`referredBy`	Relation to the user who made the referral.
`referrals`	List of all users this person has referred.
`offboardedAt`	Timestamp when user was removed from waitlist (e.g., got access).
`discardedAt`	Timestamp when user was marked as invalid or removed.
`updatedAt`	Timestamp of last record update, auto-set to current time.
`createdAt`	Timestamp when user signed up, auto-set to current time.

Key Design Decisions

Uses a self-referential relation for tracking referrals, allowing multi-level referral tracking.
Separates offboardedAt and discardedAt to distinguish between successful conversions and removed entries.
Email uniqueness prevents duplicate signups.
Includes database indexes on referralCode and email for faster lookups.
Uses cascade deletion, meaning if a referrer is deleted, all their referral connections are cleaned up.
Uses CUID instead of UUID for IDs, which is better for database performance and URL-friendly.
Keeps track of both creation and update times for audit purposes.
Makes referral tracking optional by having referredById as nullable.

Apply Changes

Remember to apply these changes to your development database and regenerate Prisma client.

npx prisma migrate dev --name create_waitlist_model

Or if you are not using migrations:

npx prisma db push

WaitlistSignUps

Key Design Decisions

Apply Changes

On this page

`WaitlistSignUps`