fix(entity): set the default value of UpdateDateColumn to CURRENT_TIMESTAMP

[gauthier-th]

Description

Fix future TypeORM migrations by explicitly setting the default value for @UpdateDateColumn to CURRENT_TIMESTAMP across all entities. This prevents migrations from incorrectly generating with datetime('now').

• Re fix(entities): replace MySQL-only onUpdate with @UpdateDateColumn #2823

How Has This Been Tested?

Try to generate a TypeORM migration before/after with:
pnpm migration:generate test

The migration after this change doesn't contain all the changes on the updatedAt columns.

Screenshots / Logs (if applicable)

N/A

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

• Chores
  • Updated database timestamp field configurations across core entities to include explicit default values, ensuring consistent initialization behavior when records are created and modified.

[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: b7593715-6493-4525-861a-0ce505379268

📥 Commits

Reviewing files that changed from the base of the PR and between 1d2aa76 and 83c3b50.

📒 Files selected for processing (10)

• server/entity/DiscoverSlider.ts
• server/entity/Issue.ts
• server/entity/IssueComment.ts
• server/entity/Media.ts
• server/entity/MediaRequest.ts
• server/entity/OverrideRule.ts
• server/entity/Season.ts
• server/entity/SeasonRequest.ts
• server/entity/User.ts
• server/entity/Watchlist.ts

---

📝 Walkthrough

Walkthrough

This PR adds a default: () => 'CURRENT_TIMESTAMP' option to the @UpdateDateColumn decorators across 10 entity files in the server/entity/ directory. Each updatedAt field now explicitly sets a database-level default timestamp, alongside its existing datetime type specification.

Changes

Cohort / File(s)	Summary
Entity Column Defaults server/entity/DiscoverSlider.ts, server/entity/Issue.ts, server/entity/IssueComment.ts, server/entity/Media.ts, server/entity/MediaRequest.ts, server/entity/OverrideRule.ts, server/entity/Season.ts, server/entity/SeasonRequest.ts, server/entity/User.ts, server/entity/Watchlist.ts	Added default: () => 'CURRENT_TIMESTAMP' to @UpdateDateColumn decorators for updatedAt fields across all entity files, providing explicit database-level default timestamp initialization.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• fix(entities): replace MySQL-only onUpdate with @UpdateDateColumn #2823: Replaced MySQL-specific DbAwareColumn usages with @UpdateDateColumn in the same entity files; this PR further extends those decorators by adding explicit database defaults.

Suggested reviewers

• 0xSysR3ll

Poem

🐰 Whiskers twitching with delight,
Timestamps now default just right,
CURRENT_TIMESTAMP flows so true,
Ten entities, all shiny new! ⏰✨

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title clearly and specifically describes the main change: adding default CURRENT_TIMESTAMP values to UpdateDateColumn decorators across all entity files.

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

---

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.}