-
Notifications
You must be signed in to change notification settings - Fork 5
Timezone
Cheryl M edited this page Jul 17, 2024
·
2 revisions
All times are stored in the database in UTC +0. In Prisma, DateTime is mapped to timestamp(3) by default for a PostgreSQL database. DateTime is in ISO8601 format,
YYYY-MM-DDTHH:mm:ss.sssZ
The timezone is always UTC (as denoted by suffix z)
using the voyage schedule as an example,
Note
Jim’s time is CDT, GMT-5 during daylight saving, and GMT-6 otherwise
For Voyage 50,
- Voyage Launch will be July 1 noon (12:00) Jim’s time
- Sprints end at 11:59pm (23:59) Sundays Jim’s time (so they would start 00:00 Mondays Jim’s time)
- Sprint check-in will due at the same time as each sprint ends (23:59 sundays Jim’s time)
- Voyage end and project due would be the same as Sprint 6 end (23:59 sundays Jim’s time)
- For solo project, completion certificates, and voyage showcase dates, exact times do not matter, so we will set it to 23:59 PST/PDT
Time Zone Converter – Time Difference Calculator - check for each voyage, as UTC time will change based on US daylight saving
Sample timezone conversion (referencing 3 different locations in the world, US, EU and AU)
e.g. voyage start for v50 (UTC time will be stored in the database)sprint 2 start
sprint 2 ends
Translated to UTC
Event | Date and Time |
---|---|
Solo project deadline | 24 Jun 06:59 |
Voyage launch | 1 Jul 17:00 (Monday) |
Sprint start | 1(17:00), 8(05:00), 15, 22, 29, 5 |
Sprint end | 8(04:59), 15, 22, 29, 5, 12 |
Voyage end | 12 Aug (04:59) |
Completion certificate | 19 Aug 06:59 |
Voyage showcase | 26 Aug 06:59 |
Prisma Schema API | Prisma Documentation
Date.prototype.toISOString() - JavaScript | MDN
JavaScript Date Tutorial: Get the Timezone Right!