# `LocalDateTime`

A date and a clock time with no zone, written `2026-10-25T09:30:00`: not one moment until a zone is chosen.

[Time and calendar](types.md#time-and-calendar); ordered; since Jadpo 0.1.0.

## Make one

Build one from its fields, `LocalDateTime { date: ...  time: ... }`.

`text.parse(raw, as: LocalDateTime)` reads one from its text; text that isn't one at all fails `malformed`, such as `2026-10-25T01:30:00Z`, `2026-10-25 01:30:00` or `2026-10-25T24:00:00`.

## Fields

| Field | Type |
|---|---|
| `date` | [`CalendarDate`](type-calendar-date.md) |
| `time` | [`LocalTime`](type-local-time.md) |

## Text, JSON and storage

`text.from` writes its canonical text, the one form `text.parse` reads back. JSON sends its canonical text as a string.

| Text | JSON |
|---|---|
| `2026-03-29T01:30:00` | `"2026-03-29T01:30:00"` |
| `2026-10-25T01:30:00` | `"2026-10-25T01:30:00"` |

It is stored in one column named for the field, of type `timestamp`. `2026-10-25T01:30:00` is stored as `'2026-10-25 01:30:00.000000'::timestamp`.

## Shown to people

`text.format(value, locale:)` shows it to people in their locale. A call also gives `format:`.

With `locale: Locale.en_gb` and `format: TimeFormat.date_time_medium`:

| Value | Shown |
|---|---|
| `2026-03-29T01:30:00` | `29 Mar 2026, 01:30:00` |
| `2026-10-25T01:30:00` | `25 Oct 2026, 01:30:00` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It is ordered, so `<` and sorting take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.