fix(migration): repair postgres blocklist id sequence

[0xSysR3ll]

Description

On PostgreSQL, the blocklist.id column is NOT NULL but has no default, even though public.blocklist_id_seq exists.
As a result, all inserts into blocklist fail with a null value in column id error making blocklist feature unusable.

This seems to have been introduced as part of #2157

• Fixes PostgreSQL: blocklist table id column missing sequence default - prevents blocklisting any media #2661

How Has This Been Tested?

• Fresh Seerr install with postgresql as DBMS

Screenshots / Logs (if applicable)

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• Bug Fixes
  • Corrected blocklist ID generation so new entries receive the proper incremental IDs and avoid collisions with existing data. A database migration synchronizes the ID sequence with current records; the rollback is intentionally left empty.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ae9ded36-3db1-4fdc-ae5a-5b8207de3e74

📥 Commits

Reviewing files that changed from the base of the PR and between 600aa7f and 4a81243.

📒 Files selected for processing (1)

• server/migration/postgres/1772000000000-FixBlocklistIdDefault.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• server/migration/postgres/1772000000000-FixBlocklistIdDefault.ts

---

📝 Walkthrough

Walkthrough

Adds a TypeORM migration that sets the default sequence for the PostgreSQL blocklist.id column and synchronizes the sequence with the current max id to restore correct auto-increment behavior.

Changes

Cohort / File(s)	Summary
PostgreSQL Migration server/migration/postgres/1772000000000-FixBlocklistIdDefault.ts	Adds migration that sets id default to nextval('public."blocklist_id_seq"') and runs setval to align the sequence with MAX(id). down is intentionally a no-op with explanatory comment.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A missing nextval hid from sight,
I hopped and fixed the sequence right,
IDs now grow in line,
Inserts hum and shine,
Blocklists bloom beneath the light 🌱

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix(migration): repair postgres blocklist id sequence' clearly and concisely describes the main change: fixing a PostgreSQL migration to repair the blocklist id sequence default, which is the primary objective of the PR.
Linked Issues check	✅ Passed	The PR successfully addresses issue #2661 by adding a migration that sets the blocklist.id column default to nextval('public.blocklist_id_seq') and synchronizes the sequence, directly fixing the root cause of INSERTs failing on PostgreSQL.
Out of Scope Changes check	✅ Passed	The PR adds only one migration file focused entirely on fixing the blocklist id sequence default and synchronization, with no unrelated or out-of-scope changes present.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

📝 Coding Plan for PR comments

• Generate coding plan

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@server/migration/postgres/1772000000000-FixBlocklistIdDefault.ts`:
- Around line 16-19: The down() migration currently drops the "id" default (in
1772000000000-FixBlocklistIdDefault.ts), which would reintroduce the broken
schema; change down(queryRunner: QueryRunner) to be a no-op (e.g., remove or
replace the ALTER TABLE ... DROP DEFAULT call so it does nothing) so rolling
back does not restore the bad state while keeping the up() fix in place; target
the down method in this migration file (method name: down, class/migration:
1772000000000-FixBlocklistIdDefault) and ensure it returns without executing any
SQL.
- Around line 11-13: The current call to queryRunner.query sets the sequence via
setval('public."blocklist_id_seq"', COALESCE((SELECT MAX("id") FROM
"blocklist"), 0), true) which can attempt to set the sequence to 0 on empty
tables; change this to set the sequence to COALESCE((SELECT MAX("id") FROM
"blocklist"), 0) + 1 and pass is_called = false so the sequence is initialized
to 1 on empty tables: locate the queryRunner.query invocation that calls setval
on 'public."blocklist_id_seq"' and update the SQL to use MAX("id") + 1 with the
third argument false.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 162a5f86-7e1e-456e-b32c-c8cdc65fb36e

📥 Commits

Reviewing files that changed from the base of the PR and between 636dcb9 and 600aa7f.

📒 Files selected for processing (1)

• server/migration/postgres/1772000000000-FixBlocklistIdDefault.ts

[Copilot]

Pull request overview

Repairs the PostgreSQL blocklist.id auto-increment behavior by attaching the existing blocklist_id_seq sequence as the column default and syncing the sequence value to current table data, restoring functional inserts for the blocklist feature.

Changes:

• Add a new PostgreSQL migration to set blocklist.id default to nextval(blocklist_id_seq).
• Initialize/synchronize blocklist_id_seq using the current MAX(blocklist.id) to avoid collisions after applying the default.

---

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

You can also share your feedback on Copilot code review. Take the survey.