add: xata db migrations

[bitfalt]

This PR does the following:

• Add xata db migrations for PublicFigure and PublicFigurePerUser for feat: added shareable results #140

Summary by CodeRabbit

• New Features
  • Introduced enhanced support for managing public figure profiles, enabling detailed tracking of public figures and their associated user data.
  • Expanded the data model with new fields to store additional public figure information, such as identifiers, names, and metrics.
  • Improved the overall data structure for a richer, more integrated experience.

[coderabbitai]

Walkthrough

This pull request solely focuses on database migration updates and schema enhancements. It adds multiple new migration entries and corresponding migration files to extend the migration ledger. The new migration scripts introduce changes to the PublicFigures and PublicFigurePerUser tables by creating tables, adding new columns (with foreign keys), and altering existing columns. Additionally, the schema definition file is updated to reflect these new tables, modified constraints, and type exports.

Changes

File(s)	Change Summary
frontend/.../migrations/.ledger	Added 10 new migration identifiers to track the new migration scripts.
frontend/.../migrations/mig_cuh562*.json<br>frontend/.../migrations/mig_cuh7dfb*.json<br>frontend/.../migrations/mig_cuh7eghi*.json<br>frontend/.../migrations/mig_cuh7f4b*.json<br>frontend/.../migrations/mig_cuh7fd9*.json	Introduced migration files related to the PublicFigures table: dropping a constraint from IdeologyPerUser and creating/altering the PublicFigures table (adding columns such as celebrity_id, name, and scores).
frontend/.../migrations/mig_cuh7l4hi*.json<br>frontend/.../migrations/mig_cuh7mbj*.json<br>frontend/.../migrations/mig_cuh7mp1*.json<br>frontend/.../migrations/mig_cuh7n71*.json<br>frontend/.../migrations/mig_cuh7vupi*.json	Introduced migration files for the PublicFigurePerUser table: creating the table, adding columns (including foreign key columns for linking with PublicFigures and Users), and altering a column (renaming from public_figure to celebrity).
frontend/.../xata.ts	Updated the schema definitions by adding new tables (PublicFigures, PublicFigurePerUser), modifying constraints (removing and updating uniqueness), and adding type exports to support these entities.

Sequence Diagram(s)

sequenceDiagram
    participant M1 as mig_cuh562...
    participant M2 as mig_cuh7dfb...
    participant M3 as mig_cuh7eghi...
    participant M4 as mig_cuh7f4b...
    participant M5 as mig_cuh7fd9...
    participant M6 as mig_cuh7l4hi...
    participant M7 as mig_cuh7mbj...
    participant M8 as mig_cuh7mp1...
    participant M9 as mig_cuh7n71...
    participant M10 as mig_cuh7vupi...

    M1->>M2: Initiate PublicFigures table migration
    M2->>M3: Add column (celebrity_id) to PublicFigures
    M3->>M4: Add column (name) to PublicFigures
    M4->>M5: Add column (scores) to PublicFigures
    M5->>M6: Create PublicFigurePerUser table
    M6->>M7: Add column (public_figure) with FK to PublicFigures
    M7->>M8: Add column (celebrity_user_id) to PublicFigurePerUser
    M8->>M9: Add column (user) with FK to Users in PublicFigurePerUser
    M9->>M10: Alter column (rename public_figure to celebrity)

Loading

Possibly related PRs

• feat: xata migrations and payment endpoint #99: Involves migration entries and schema expansion, including new tables, similar to the PublicFigures and PublicFigurePerUser changes.
• feat: add ideology insights, fetch pay amount and user level, points from db #136: Contains modifications to the migration ledger and adds migration files for schema changes, notably affecting the IdeologyPerUser table.

Suggested reviewers

• evgongora

Poem

(_/) Hop into migrations, oh so bright,
( •_•) Tables bloom into digital light.
New columns and schemas join the parade,
Every line of code carefully laid.
With leaps of joy, my rabbit heart sings,
Code hops forward on innovative wings!

---

📜 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 2ef70b9 and 15b78c3.

📒 Files selected for processing (12)

• frontend/.xata/migrations/.ledger (1 hunks)
• frontend/.xata/migrations/mig_cuh562rrr2giaepaghv0.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7dfbrr2giaepagif0.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7eghi7viit4iimuv0.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7f4brr2giaepagij0.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7fd9i7viit4iimv00.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7l4hi7viit4iimvag.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7mbjrr2giaepagis0.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7mp1i7viit4iimvcg.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7n71i7viit4iimvdg.json (1 hunks)
• frontend/.xata/migrations/mig_cuh7vupi7viit4iimvgg.json (1 hunks)
• frontend/src/lib/xata.ts (4 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Code Quality & Build
• GitHub Check: Bundle Analysis

🔇 Additional comments (22)

frontend/.xata/migrations/.ledger (1)

119-128: LGTM!

The migration identifiers are properly ordered and follow the expected naming convention.

frontend/src/lib/xata.ts (4)

448-448: LGTM!

Removing the unique constraint from the user column in IdeologyPerUser table is correct, as it allows users to have multiple ideologies.

---

914-1006: LGTM!

The PublicFigurePerUser table is well-structured with:

• Proper foreign key constraints to PublicFigures and Users tables
• Required columns: celebrity, celebrity_user_id, user
• Appropriate uniqueness and nullability constraints

---

1007-1086: LGTM!

The PublicFigures table is well-structured with:

• Required columns: celebrity_id, name, scores
• Appropriate unique constraints on name and xata_id
• JSON type for scores to store flexible data

---

2025-2030: LGTM!

The type definitions for the new tables are properly exported:

• Types: PublicFigurePerUser, PublicFigures
• Record types: PublicFigurePerUserRecord, PublicFiguresRecord
• Database schema updated to include the new tables

Also applies to: 2065-2066

frontend/.xata/migrations/mig_cuh7vupi7viit4iimvgg.json (1)

1-20: LGTM!

The migration to rename the column from 'public_figure' to 'celebrity' is well-structured with:

• Proper operation type and parameters
• Correct parent migration reference
• Required metadata (schema, timestamp)

frontend/.xata/migrations/mig_cuh562rrr2giaepaghv0.json (1)

1-21: LGTM!

The migration to drop the unique constraint is well-structured with:

• Proper operation type and parameters
• Both up and down directions specified
• Correct parent migration reference
• Required metadata (schema, timestamp)

frontend/.xata/migrations/mig_cuh7fd9i7viit4iimv00.json (1)

1-24: JSON Structure and Default Value for scores:
The structure is clear and the migration operation to add the scores column (of type json) to the PublicFigures table is well-defined. Please verify that the "up": "'{}'" value is correctly interpreted by your migration engine as an empty JSON object.

frontend/.xata/migrations/mig_cuh7eghi7viit4iimuv0.json (1)

1-24: Migration for Adding celebrity_id:
This migration correctly introduces the celebrity_id column (type int) to the PublicFigures table. Ensure that using "up": "0" as the default value meets your data initialization needs and aligns with the migration system’s requirements.

frontend/.xata/migrations/mig_cuh7mp1i7viit4iimvcg.json (1)

1-24: Migration for Adding celebrity_user_id:
The addition of the celebrity_user_id column (type int) to the PublicFigurePerUser table is implemented as expected. As with the previous migration, confirm that the default "up": "0" is intentional and consistent with your overall schema design.

frontend/.xata/migrations/mig_cuh7f4brr2giaepagij0.json (1)

1-25: Adding Unique name Column to PublicFigures:
This migration adds a name column (type text) with a uniqueness constraint to the PublicFigures table. Please verify that the default value defined by "up": "''" (an empty string) is appropriate for your use case.
Consider whether an empty string is acceptable for a unique field or if making the column nullable (or providing a different default) might better prevent potential conflicts in pre-existing data.

frontend/.xata/migrations/mig_cuh7n71i7viit4iimvdg.json (1)

1-30: Adding user Column with Foreign Key Constraint:
This migration adds a user column (type text) to the PublicFigurePerUser table with an appropriate foreign key reference to the Users table (via the xata_id column), and it specifies an on_delete behavior of SET NULL.
Please check that the default "up": "''" (empty string) is the intended initialization, and that the types for this column and the referenced Users.xata_id are compatible to avoid any runtime issues.

frontend/.xata/migrations/mig_cuh7mbjrr2giaepagis0.json (2)

7-22: Review: Validate 'up' field in the add_column operation.
The operation correctly defines the addition of the public_figure column (type: text) along with its foreign key reference to PublicFigures(xata_id), and includes a proper comment attribute. However, the "up" field is set to an empty string ("''"), which might be intentional as a no-op placeholder but should be confirmed to ensure that the migration system applies the desired schema change correctly.

---

23-30: Review: Migration Metadata Consistency.
The metadata section (fields "done", "migrationType", "name", "parent", "schema", and "startedAt") is clearly defined and follows the expected format. No issues found here.

frontend/.xata/migrations/mig_cuh7dfbrr2giaepagif0.json (4)

7-37: Review: Creation of PublicFigures Table.
The migration creates the PublicFigures table with the required columns (xata_id, xata_version, xata_createdat, and xata_updatedat). The check constraint on xata_id and its default value using the expression "'rec_' || xata_private.xid()" are consistent with the schema conventions observed in related migrations.

---

38-42: Review: Replica Identity SQL Operation.
The SQL statement "ALTER TABLE \"PublicFigures\" REPLICA IDENTITY FULL" is correctly placed to ensure that the table supports full logical replication, which is important for tracking data changes.

---

44-48: Review: Metadata Trigger SQL Operation.
The migration creates a trigger (xata_maintain_metadata_trigger_pgroll) that executes the function xata_private.maintain_metadata_trigger_pgroll() before INSERT or UPDATE events. Please verify that the trigger function exists and operates as intended.

---

52-57: Review: Migration Metadata.
The metadata fields, including "migrationType", "name", "parent", "schema", and "startedAt", are accurate and adhere to the standard used across migrations.

frontend/.xata/migrations/mig_cuh7l4hi7viit4iimvag.json (4)

7-36: Review: Creation of PublicFigurePerUser Table.
The migration correctly defines the PublicFigurePerUser table with its essential columns:

• xata_id: Defined as text with a check constraint to enforce length and a unique default value.
• xata_version, xata_createdat, and xata_updatedat: All follow the established schema conventions.
  This design is consistent with similar tables in the codebase.

---

38-42: Review: Replica Identity SQL Operation.
The SQL operation to set the replica identity for the table (ALTER TABLE "PublicFigurePerUser" REPLICA IDENTITY FULL) is correctly implemented, ensuring proper support for logical replication.

---

44-48: Review: Metadata Trigger SQL Operation.
The SQL command to create the trigger that maintains metadata (xata_maintain_metadata_trigger_pgroll) is consistent with best practices observed in the project. Please ensure that the function xata_private.maintain_metadata_trigger_pgroll() is available and functions as expected in your environment.

---

52-57: Review: Migration Metadata.
The migration file’s metadata (including "migrationType", "name", "parent", "schema", and "startedAt") is clear and adheres to the required schema conventions.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[netlify]

✅ Deploy Preview for lucent-florentine-971919 ready!

Name	Link
🔨 Latest commit	15b78c3
🔍 Latest deploy log	https://app.netlify.com/sites/lucent-florentine-971919/deploys/67aa3454ce00bd0007448a84
😎 Deploy Preview	https://deploy-preview-142--lucent-florentine-971919.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.

[evgongora]

LGTM!