Skip to content

Conversation

@vm-001
Copy link
Collaborator

@vm-001 vm-001 commented Jul 8, 2025

Summary

When Postgres is not UTC timezone, both created_at and updated_at do not accurately reflect the actual time because the default value of them is CURRENT_TIMESTAMP(3) AT TIME ZONE 'UTC', causing timestamp to be cast to UTC

… actual time when the database time zone was not UTC.
@codecov
Copy link

codecov bot commented Jul 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Flag Coverage Δ
integration 75.65% <ø> (?)
unit 11.54% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 108 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@vm-001 vm-001 changed the title fix(db): created_at and updated_at are not accurately reflect the actual time when the database time zone was not UTC fix(db): created_at and updated_at are not accurately reflect the actual time when database time zone was not UTC Jul 8, 2025
@vm-001 vm-001 changed the title fix(db): created_at and updated_at are not accurately reflect the actual time when database time zone was not UTC fix(db): created_at and updated_at didn't accurately reflect the actual time when database time zone was not UTC Jul 8, 2025
@webhookx-x webhookx-x merged commit a30c901 into main Jul 8, 2025
10 of 12 checks passed
@webhookx-x webhookx-x deleted the fix/database-timestamp branch July 8, 2025 03:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants