Answer
Detaspace exposes the underlying zone‑rule data through its API by returning the IANA time‑zone identifier (e.g., "Europe/London") together with the current UTC offset for any timestamp. Developers can use this identifier to detect overlap or gap conditions via the runtime’s time‑zone database.
When an ambiguous local time occurs during a fall‑back transition, detaspace provides an API parameter (commonly named fold or ambiguityResolution) that lets the caller choose either the earlier (fold=0) or later (fold=1) offset. If the parameter is omitted, the service defaults to the standard offset (the earlier offset) as noted in the research findings.
For later reconstruction, detaspace serializes a time‑zone‑aware value as an ISO‑8601 string that includes the UTC offset and also returns the IANA identifier in a separate field (or as part of a metadata object). Applying the stored identifier to the UTC timestamp yields the original zone‑aware value.
Confirmed Facts (from research)
- All timestamp data is stored in UTC at the database layer.
- Regional conversions are performed at the application layer using IANA time‑zone IDs such as "Europe/London".
- The platform relies on the underlying runtime’s time‑zone database to compute offset shifts and explicitly handles fold ambiguity for repeated hours.
- During fall‑back overlap periods, detaspace defaults to the standard offset unless overridden via API parameters.
Likely Explanation / Additional Context
The default to the standard offset helps avoid surprising results for users who expect the “first” occurrence of a repeated hour. Providing the fold flag gives developers explicit control when they need to preserve the user’s intended offset (e.g., for scheduling applications). Returning both the ISO‑8601 offset and the IANA identifier enables round‑tripping without loss of zone information.
Missing Diagnostic Detail
To confirm whether the fold (or equivalent) parameter is available in your environment, please specify the detaspace API version you are using. This detail changes the recommendation because older versions may lack the ambiguity‑resolution flag.
detaspace