chore: upgrade to prisma v5

[Krish120003]

Summary by CodeRabbit

• New Features
  • Introduced new user roles and statuses.
  • Added new tables for account management, user reviews, and session tracking.
  • Implemented event logging and verification token systems.
• Refactor
  • Switched database provider from PostgreSQL to CockroachDB.
  • Updated data annotations in Account and User models for better data management.
  • Enhanced Review model with explicit hacker and reviewer fields.

[coderabbitai]

Walkthrough

The recent changes encompass the creation of new ENUM types, tables, and unique indexes in the SQL migration file. The Prisma schema has been updated with changes in the datasource provider, removal of certain annotations, addition of new fields, and a new model.

Changes

File	Summary
prisma/migrations/0_init/migration.sql	Introduced two ENUM types, "Role" and "Status". Created five new tables: "Account", "Session", "User", "Review", "EventLog", and "VerificationToken". Added unique indexes and foreign key constraints.
prisma/schema.prisma	Changed datasource provider from "postgresql" to "cockroachdb". Removed @db.Text annotation from several fields in the Account and User models. Added hacker and reviewer fields to the Review model. Introduced the VerificationToken model.

Poem

🍂 As the autumn leaves fall, we code with glee, 🍁

Changes abound, as you can clearly see. 🖥️

New tables and types, a schema so fine, 📚

In the world of Prisma, everything's divine. 🌐

From Postgres to Cockroach, a leap we've made, 🐇

Fear not, for our code is grade-A grade. 🏆

So here's to the changes, big and small, 🥂

In the world of code, we stand tall. 🌟

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai help to get help.
• @coderabbitai resolve to resolve all the CodeRabbit review comments.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

[netlify]

✅ Deploy Preview for profound-kringle-30b3e4 ready!

Name	Link
🔨 Latest commit	508873b
🔍 Latest deploy log	https://app.netlify.com/sites/profound-kringle-30b3e4/deploys/6545e3ae5771c30008c4e91b
😎 Deploy Preview	https://deploy-preview-150--profound-kringle-30b3e4.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between aff79ff and 508873b.

Files ignored due to filter (3)

• package-lock.json
• package.json
• prisma/migrations/migration_lock.toml

Files selected for processing (2)

• prisma/migrations/0_init/migration.sql (1 hunks)
• prisma/schema.prisma (6 hunks)

Additional comments: 10

prisma/migrations/0_init/migration.sql (4)

• 1-6: The creation of new ENUM types "Role" and "Status" is a good practice for maintaining data integrity and consistency. Ensure that the values of these ENUMs are used consistently throughout the application.

• 77-81: The creation of new tables "Account", "Session", "User", "Review", "EventLog", and "VerificationToken" is a significant change. Ensure that these tables are properly integrated into the application and that all necessary relationships are established.

• 84-99: The creation of unique indexes is a good practice for optimizing database performance and ensuring data integrity. Ensure that these indexes are used correctly in the application.

• 102-114: The addition of foreign key constraints is a good practice for maintaining data integrity and consistency. Ensure that these constraints are handled correctly in the application, especially in the case of cascading deletes or updates.

prisma/schema.prisma (6)

• 1-8: The datasource provider has been changed from "postgresql" to "cockroachdb". Ensure that the CockroachDB is set up correctly and the DATABASE_URL environment variable is updated accordingly.

• 14-28: The @db.Text annotations have been removed from several fields in the Account model. This could potentially affect the way data is stored and retrieved. Ensure that this change is compatible with the data types of the corresponding columns in the database.

• 46-52: The User model has been updated with new relation fields hacker and reviewer for the Review model. Ensure that these changes are reflected in the corresponding database schema and that the relations are set up correctly.

• 60-68: The Review model has been updated with explicit hacker and reviewer fields with @relation annotations. Ensure that these changes are reflected in the corresponding database schema and that the relations are set up correctly.

• 78-84: A new VerificationToken model has been added. Ensure that this model is reflected in the corresponding database schema and that the unique constraints are set up correctly.

• 101-103: New ENUM values have been added to the Status ENUM. Ensure that these changes are reflected in the corresponding database schema.