Profiles & cities

legacy_follows

Legacy follows from v4 that couldn't be resolved to a profile or dancer during the Step 15 migration. Kept for provenance; no app code reads this.

Columns

Column	Type	Null	Default	Keys
id	uuid	no	gen_random_uuid()	PK
dancer_id	uuid	no	—	→ dancers.id
target_username	text	no	—
source	text	no	"v4"
created_at	timestamp	yes	now()

Value lists come from .$type<'a' | 'b'>() in the schema — enforced in TypeScript only, not by the database.

Keys, constraints & indexes

Unique

(dancer_id, target_username) legacy_follows_dancer_target

Indexes

No secondary indexes.

Foreign keys

dancer_id → dancers.id
on delete no action

Used by

Code that reads or writes this table, found by static analysis of the tRPC routers and API handlers (including helpers they call).

tRPC procedures

No public or signed-in procedure.

REST & webhooks

None.

Relations

Rendering diagram…

Diagram source

erDiagram
  dancers {
    uuid id PK
    text email UK
    text neon_auth_id UK
    text username UK
  }
  legacy_follows {
    uuid id PK
    uuid dancer_id FK
  }
  dancers ||--o{ legacy_follows : "dancer_id"

Defined at server/database/schema.ts:990 as legacyFollows.

Columns #

Keys, constraints & indexes #