ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Assumes Liquibase 4.x targeting PostgreSQL, MySQL, and Oracle. The goal is to store logical event timestamps consistently across vendors without regional wall-clock drift when changelogs run from application servers in different time zones. Liquibase has no standalone change-type attribute that forces UTC storage, so conversion is delegated to the target dat
NetBox persists timestamps in PostgreSQL as UTC and renders them in the web UI according to each user's preferred time zone, defaulting to the installation-wide TIME_ZONE setting when no preference is set. The REST API serializes datetime fields as ISO 8601 strings in UTC, leaving regional interpretation to the client. The dcim.Site model includes an optiona
Goal Ensure that changing the time zone through Linux Mint’s Cinnamon Date & Time settings leaves the hardware clock (RTC) in a state that is consistent with the chosen zone and with systemd’s NTP synchronization. Background The Cinnamon GUI writes the zone to /etc/localtime and updates systemd-timedated , but it does not explicitly adjust the RTC mode v
Goal: enable conversion of a POSIX timestamp to a broken‑down time in an arbitrary time zone without mutating the process TZ variable, while remaining safe for concurrent calls. Constraint: Unix.localtime and Unix.gmtime rely on the C library’s tzdata and modify a shared static struct, making them unsafe in multi‑threaded code; the standard library offers no
Context I am designing date handling for an iOS app (Xcode 15+, Swift, targeting iOS 15 and later) that stores event times on a server and displays them to users who travel across regional time zones. The hard constraint is that stored values must round-trip deterministically, while the UI must always reflect the user's current device time zone. The trade-of
Vert.x PostgreSQL Client 4.x – TIMESTAMPTZ Mapping The client maps PostgreSQL TIMESTAMPTZ to java.time.OffsetDateTime and TIMESTAMP to java.time.LocalDateTime . The offset is preserved, but the JVM default zone or the database session time zone can alter the perceived value when read back or serialized to JSON. Unresolved Decision Should the application stor
In Firebird 4.0+, the TIMESTAMP WITH TIME ZONE type allows for storage using both numeric UTC offsets and IANA region names (e.g., 'Europe/Berlin'). While the engine normalizes these values to UTC for comparison and sorting purposes, the long-term behavior differs significantly based on the input format. When an IANA region name is stored, the engine evaluat
Problem Statement The brew info --json=v2 command exposes created_at and updated_at fields as ISO 8601 strings ending with a Z , indicating UTC. Homebrew’s documentation states that these timestamps are not adjusted for the user’s local time zone. Unresolved Decision It is unclear whether Homebrew will ever support a local‑time view of these fields or provid
Goal: Confirm whether FusionAuth validates a user profile time zone ID before accepting it, or whether an unrecognized ID silently falls back to the JVM default time zone. Research context indicates FusionAuth stores internal timestamps in UTC and applies a configured time zone only at presentation layers such as the admin UI and email templates. It also sug
liquibase
linuxmint
ocaml
unix
xcode
vertx
firebird
homebrew