Skip to content

Make Device.id the primary key #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adamshiervani merged 1 commit into from
Nov 6, 2026
Merged

Make Device.id the primary key #94

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions prisma/migrations/20261106140000_device_primary_key/migration.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
-- Device.id becomes the primary key. The existing unique index on "id" is
-- reused, so Postgres renames it to "Device_pkey" without rebuilding it. The
-- column is already NOT NULL, so no table scan is needed.
ALTER TABLE "Device" ADD CONSTRAINT "Device_pkey" PRIMARY KEY USING INDEX "Device_id_key";
2 changes: 1 addition & 1 deletion prisma/schema.prisma
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ model User {
}

model Device {
id String @unique
id String @id
lastSeen DateTime? @db.Timestamp(6)
name String?
user User @relation(fields: [userId], references: [id])
Expand Down
Loading