Skip to content

feat: merge date and zerotime into single field#292

Merged
martinkrivda merged 4 commits intomainfrom
feature/merge-zerotime-and-date
Apr 28, 2026
Merged

feat: merge date and zerotime into single field#292
martinkrivda merged 4 commits intomainfrom
feature/merge-zerotime-and-date

Conversation

@lukaskett
Copy link
Copy Markdown
Contributor

Summary

  • Keeps iso8601 approach, also removes ambiguity of the date field, which when converted to local date-time might end up in the day before, Settings review #165

Checklist

  • I linked the related issue or explained why none is needed.
  • I ran the relevant checks for this change.
  • I updated documentation or changelog entries when needed.
  • By submitting this pull request, I agree to the terms in CLA.md in the
    repository root.

@lukaskett
Copy link
Copy Markdown
Contributor Author

Unify date of the event in the Event Information card and date on the Event Link card, the format is slightly different - #165 .

It looks that the first one respects system setup and the second one is static/fixed.

@@ -0,0 +1,7 @@
-- Merge separate date (DATE) and zeroTime (TIME) columns into a single DATETIME column.
-- The new `date` stores the UTC event start timestamp.
ALTER TABLE `event` ADD COLUMN `date_tmp` DATETIME(3) NOT NULL DEFAULT '1970-01-01 00:00:00.000';
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to record the event time in milliseconds with three decimal places of precision? Since the event will likely always start on the minute, I believe DATETIME(0) is a more appropriate choice.

@martinkrivda martinkrivda merged commit c6ba371 into main Apr 28, 2026
1 of 3 checks passed
@martinkrivda martinkrivda deleted the feature/merge-zerotime-and-date branch April 28, 2026 05:32
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.

2 participants