Date/time types

Typo uses its own wrapper types for date/time, which delegates to java.time.

For timetz, OffsetTime is used. For timestamptz, Instant is used, since PostgreSQL store these timestamps in UTC.

See typo-types for some motivation for why the wrapper types were necessary.

The most important reason was that the PostgreSQL driver loses precision and offsets, and for accuracy it's important to avoid that code path. To that end, values are transferred as strings. You can make use of these data types outside of Typo if cast to ::text explicitly in sql.

With Typo you can round-trip rows with Instant and the resulting row will compare equal to the one you inserted.

Ref arrays, arrays of date/times are usable if you define such a column.

import java.time.*

/** This is `java.time.TypoInstant`, but with microsecond precision and transferred to and from postgres as strings. The reason is that postgres driver and db libs are broken */
case class TypoInstant(value: Instant)
/** This is `java.time.LocalDate`, but transferred to and from postgres as strings. The reason is that postgres driver and db libs are broken */
case class TypoLocalDate(value: LocalDate)
/** This is `java.time.LocalDateTime`, but with microsecond precision and transferred to and from postgres as strings. The reason is that postgres driver and db libs are broken */
case class TypoLocalDateTime(value: LocalDateTime)
/** This is `java.time.LocalTime`, but with microsecond precision and transferred to and from postgres as strings. The reason is that postgres driver and db libs are broken */
case class TypoLocalTime(value: LocalTime)
/** This is `java.time.OffsetTime`, but with microsecond precision and transferred to and from postgres as strings. The reason is that postgres driver and db libs are broken */
case class TypoOffsetTime(value: OffsetTime)