DB schema for connection events and attendance

Summary

Set up connection_event and hackathon_attendance tables.

Contexts

Foundation for both streak types. Receiver privacy rule: receiver_id only stored with consent.

Tasks

Create connection_event table per spec
Create hackathon_attendance table per spec
Enforce receiver_id is only ever set when receiver is signed in and consents

Acceptance Criteria

Migrations run cleanly
Anonymous connections never write a receiver_id
Tests added
docs updated

Area

backend

Difficulty

Good first issue

@ShantKhatri

Hi @ShantKhatri,

Thanks for opening this issue.

Please reply with one of the following areas so the issue can be routed to the appropriate team member:

- /backend
- /web
- /mobile
- /devops

Once an area is selected, the corresponding label will be added automatically.

@ShantKhatri

I would like to work on this @ShantKhatri

@Satvik-art-creator

@Satvik-art-creator I have assigned this issue to you.

Navigation Menu

Repository navigation

DB schema for connection events and attendance #689

Summary

Contexts

Tasks

Acceptance Criteria

Area

Difficulty

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

DB schema for connection events and attendance #689

Description

Summary

Contexts

Tasks

Acceptance Criteria

Area

Difficulty

Activity

github-actions commented on Jul 12, 2026

Satvik-art-creator commented on Jul 15, 2026

Harxhit commented on Jul 15, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions