ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
An Elixir application using Ecto with PostgreSQL needs to store all timestamps as UTC via :utc_datetime / timestamptz while accepting and presenting values in a per-user regional time zone. tzdata is available for Calendar.DateTime.shift_zone/3. Ecto does not perform automatic regional conversion. The documented pattern is UTC storage in the database with co
Goal I want to convert a local wall-clock time to UTC using Gleam's DateTime module, which relies on the Erlang VM's timezone database. The conversion should work for a named IANA zone such as "Europe/Berlin", including dates that fall inside a daylight-saving transition. Constraints and uncertainty The conversion API requires an explicit timezone identifier
Unresolved naive datetime rendering in the Python debugger PyCharm's debugger displays timezone-aware datetime objects with their UTC offset, but naive datetime objects are rendered in the configured IDE time zone without any visual indicator that they lack timezone information. An open YouTrack issue debates whether naive datetimes should be assumed UTC or
The goal is to allow Prisma schema definitions to store offset‑aware timestamps directly in the database, preserving the original time‑zone information instead of converting everything to UTC. Currently, Prisma maps DateTime fields to UTC‑only types (e.g., TIMESTAMP without time zone in PostgreSQL) and discards any offset supplied in input values, requiring
A MariaDB schema must handle event logging across multiple regional time zones while ensuring data remains consistent during daylight savings transitions. The goal is to maintain a reliable audit trail that can be retrieved in the local time of the event origin. Two documented approaches exist: using TIMESTAMP columns, which automatically handle UTC conversi
Date/time handling in ShotGrid API ShotGrid stores all timestamp fields internally in UTC and the REST API returns ISO 8601 strings without any explicit timezone offset. The web UI automatically converts these values to the user’s local time zone based on browser or profile settings. This design leaves a gap for client applications: they must assume UTC and
When storing timestamps via Ti.App.Properties.setString() , the ISO string produced by JSON.stringify(new Date()) is always UTC (ending in Z ). If the device timezone changes between write and read — for example, the user travels or the system applies a DST transition — parsing the stored string with new Date(storedString) yields a different local offset tha
XML Schema dateTime values without timezone offsets present interpretation challenges in distributed systems. The W3C XML Schema specification defines dateTime as accepting an optional timezone component, where omitting it indicates local time without offset information. This creates ambiguity when documents move between regions with different local times. J
Goal Determine how MATLAB's datetime class resolves ambiguous local times during fall-back DST transitions and how the version of the bundled IANA time zone database affects this behavior across different releases. Constraints and Uncertainty Since R2020b, the AmbiguousTime parameter allows selecting 'first', 'last', or 'error', but the default behavior sile
ecto
gleam
prisma
shotgrid
titaniumsdk