feat(db): switch timestamps to timestamptz #1773
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

TL;DR
Update all timestamp columns in the database to use timezone information.
What changed?
This PR modifies all timestamp columns across database tables to use
timestamp with time zonedata type instead of the default timestamp without timezone. It also ensures that timestamp columns have a default value ofnow()where appropriate.The changes affect the following tables:
How to test?
Why make this change?
Using timezone-aware timestamps ensures consistent time handling across different environments and regions. This prevents issues with time calculations and comparisons that can occur when timestamps lack timezone information, especially in a distributed system where users or services may be in different timezones.