chage db schema for psqldf

[lirlia]

change db schema for psqldf (data structure is not changed)

• related add database migration  #6
• sqldef/sqldef: Idempotent schema management for MySQL, PostgreSQL, and more

❯ psqldef --password password prel < db/schema.sql

-- Apply --
CREATE TABLE iam_role_filtering_rules (
    id TEXT PRIMARY KEY NOT NULL,
    pattern TEXT NOT NULL,
    user_id TEXT NOT NULL REFERENCES users(id),
    created_at TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT CURRENT_TIMESTAMP,
    updated_at TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT CURRENT_TIMESTAMP
);

Summary by CodeRabbit

• Refactor
  • Improved consistency in timestamp handling across various tables in the database.

[coderabbitai]

Walkthrough

The recent modifications involve a standardization of timestamp data types across various tables in the database schema. Fields that previously used TIMESTAMPTZ have been updated to TIMESTAMP WITH TIME ZONE, ensuring consistent handling of time zone information within timestamp values.

Changes

Files	Change Summary
db/schema.sql	Changed timestamp fields from TIMESTAMPTZ to TIMESTAMP WITH TIME ZONE for users, requests, invitations, iam_role_filtering_rules tables.

🐇💻🌟

In the schema fields, time does dance,
With zones in its step, a uniform prance.
A rabbit's delight, as timestamps align,
Code hops through the fields, with a tweak so fine.
🎉🕒🌐

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 with CodeRabbit Bot (@coderabbitai)

• You can directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• You can tag CodeRabbit on specific lines of code or entire files in the PR by tagging @coderabbitai in a comment. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• You can tag @coderabbitai in a PR comment and ask questions about the PR and the codebase. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid.
  • @coderabbitai read the files in the src/scheduler package and generate README in the markdown format.

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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 1a4124a and 502ffbe.

Files selected for processing (1)

• db/schema.sql (1 hunks)

Additional comments: 4

db/schema.sql (4)

• 8-11: The change from TIMESTAMPTZ to TIMESTAMP WITH TIME ZONE for the session_expired_at, last_signin_at, created_at, and updated_at fields in the users table is consistent with the PR's objective to standardize timestamp fields across the database. Ensure that any application logic that reads or writes to these fields is aware of the change in data type.

• 16-26: The requests table shows the addition of foreign key references and the change in timestamp fields. Verify that the foreign key constraints (requester_user_id and judger_user_id) do not introduce any referential integrity issues with existing data. Also, confirm that the application logic that interacts with the requested_at, expired_at, judged_at, created_at, and updated_at fields accommodates the new timestamp data type.

• 31-37: The invitations table has been updated with foreign key references and timestamp data type changes. Ensure that the foreign key (inviter_user_id) is correctly set up and that the application code that uses the invited_at, expired_at, created_at, and updated_at fields is compatible with the TIMESTAMP WITH TIME ZONE data type.

• 43-45: The iam_role_filtering_rules table is a new addition and includes a foreign key reference to the users table. Confirm that the user_id field is correctly referencing the users table and that the created_at and updated_at fields are being used correctly in the application with the new timestamp data type.