Claudio/squash migrations

[claudfuen]

Summary by CodeRabbit

• New Features

  • Introduced a centralized database identifier system that uses custom, human-friendly prefixes for various records.
  • Enhanced evidence management by adding new status fields for publication and relevance tracking.

• Chores

  • Streamlined and consolidated database schema components for improved data integrity and performance.
  • Removed obsolete schema elements and refined foreign key relationships and indexing to boost maintainability.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
app	❌ Failed (Inspect)			Apr 3, 2025 4:38pm
comp-portal	❌ Failed (Inspect)			Apr 3, 2025 4:38pm

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

A new Prisma configuration file has been added that specifies rules for ID generation, and a SQL function generate_prefixed_cuid has been introduced to create unique identifiers with custom prefixes. Multiple migration files have been either removed or updated, affecting table structures, enum types, indexes, and foreign key constraints. Prisma schema files have been modified to use the new database‐generated ID mechanism via dbgenerated() calls, and custom extension files for ID manipulation were removed, indicating a shift towards centralized ID generation directly from the database.

Changes

File(s)	Change Summary
.cursor/rules/prisma.mdc	Added a new configuration file for Prisma rules that defines ID generation using generate_prefixed_cuid.
packages/db/prisma/functionDefinition.sql	Introduced the SQL function generate_prefixed_cuid(prefix text) to generate unique IDs by combining a prefix, timestamp, and random hexadecimal string.
packages/db/prisma/migrations/*	Multiple migration files: Deleted or updated migration scripts affecting table schemas (e.g., Task, Organization, Evidence, EmployeeTrainingVideoCompletion), enum types (e.g., TaskStatus, Role, RequirementId), indexes, and foreign key constraints; one new migration adds the pgcrypto extension and new tables/enums.
packages/db/prisma/schema/*	Prisma schema updates: Multiple models (Artifact, Auth, Control, Evidence, Framework, Integration, Organization, Policy, Requirement, Risk, Task, Vendor, etc.) now use dbgenerated("generate_prefixed_cuid('<prefix>'::text)") for ID fields and update related enum/role definitions.
packages/db/src/extensions/generate-id-extension.{js,ts}	Removed custom ID generation extension files that previously intercepted create/upsert operations for ID manipulation.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Prisma
    participant PostgreSQL
    Client->>Prisma: Request to create a new record (ID omitted)
    Prisma->>PostgreSQL: Insert record using default: dbgenerated("generate_prefixed_cuid('<prefix>'::text)")
    PostgreSQL->>generate_prefixed_cuid: Call function with specified prefix
    generate_prefixed_cuid-->>PostgreSQL: Return generated unique ID
    PostgreSQL-->>Prisma: Return new record with generated ID
    Prisma-->>Client: Respond with inserted record (including ID)

Loading

Possibly related PRs

• add baseline migrations #48: The changes in the main PR introduce a new configuration file for ID generation using the generate_prefixed_cuid function, which is directly related to this PR that adds the same function in the SQL migration file.
• Improved Vendor Table #153: The changes in the main PR introduce a new configuration for ID generation using the generate_prefixed_cuid function, which relates to this PR that also introduces this function in the SQL migration, indicating a direct connection at the code level.
• Mariano/deel import #110: The changes in the main PR introduce a new configuration file for ID generation using the generate_prefixed_cuid function, which is related to this PR that adds this function in the SQL file, as both directly involve modifications to the ID generation mechanism.

Poem

I'm a rabbit, hopping through code so neat,
With a prefix in my stride and IDs that can't be beat.
The SQL sings a function, a rhythmic, clever tune,
Prisma now dances to a new database croon.
Migration trails vanish as order takes flight,
I'm bounding in the schema, coding day and night,
Hoppy cheers to changes that make our IDs shine bright!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 329278b and 7c375b1.

📒 Files selected for processing (38)

• .cursor/rules/prisma.mdc (1 hunks)
• packages/db/prisma/functionDefinition.sql (1 hunks)
• packages/db/prisma/migrations/20250401202048_init_123/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250401202813_add_times/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250401202832_unified_tasks/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250401203413_unified_tasks/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250401204025_unified_tasks_again/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250401204249_added_indeces/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250401210139_remove_website/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250401212359_task/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250401212450_add_role_enum/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250402162650_added_owner_role/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250402172955_roles/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250402173418_permissions/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250402185150_added_requirements_map/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250402200849_completed_at_is_optional/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250402201730_prevent_duplicates/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250402202340_yes/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250403150029_update_evidence_statuses/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250403150143_update_enum/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250403152616_assignee_should_be_member_not_user/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250403153215_idk/migration.sql (0 hunks)
• packages/db/prisma/migrations/20250403163138_init/migration.sql (26 hunks)
• packages/db/prisma/schema/artifact.prisma (1 hunks)
• packages/db/prisma/schema/auth.prisma (7 hunks)
• packages/db/prisma/schema/control.prisma (1 hunks)
• packages/db/prisma/schema/evidence.prisma (1 hunks)
• packages/db/prisma/schema/framework.prisma (1 hunks)
• packages/db/prisma/schema/integration.prisma (2 hunks)
• packages/db/prisma/schema/organization.prisma (1 hunks)
• packages/db/prisma/schema/policy.prisma (1 hunks)
• packages/db/prisma/schema/requirement.prisma (1 hunks)
• packages/db/prisma/schema/risk.prisma (1 hunks)
• packages/db/prisma/schema/schema.prisma (2 hunks)
• packages/db/prisma/schema/task.prisma (1 hunks)
• packages/db/prisma/schema/vendor.prisma (2 hunks)
• packages/db/src/extensions/generate-id-extension.js (0 hunks)
• packages/db/src/extensions/generate-id-extension.ts (0 hunks)

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.