Skip to content

v11.0.0-rc.2

v11.0.0-rc.2: Fix date/time mapping round-tripping and cloning (#4022)
@roji roji tagged this 18 Oct 21:16 
* Fix date/time mapping round-tripping and cloning

Preserve ZonedDateTime zones in JSON independently of SQL formatting, retain timetz offset minutes, and correct LocalDateTime and Interval multirange cloning.

Fixes #4018

Fixes #4019

Fixes #4020

Fixes #4021

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe

* Keep previously readable UTC ZonedDateTime JSON working

Try the original pattern if the new zone-aware JSON pattern does not match, preserving UTC documents already stored by the provider.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe

* Handle zone-aware ZonedDateTime JSON in queries

Convert extracted JSON text using the serialized offset before materializing timestamptz values. Apply the mapping-specific conversion to JSON scalars, recordsets and primitive collection elements, and avoid JSON containment for values with a custom representation.

Cover predicates, projections, nulls, DST overlaps, collection indexing, containment, DISTINCT and legacy UTC documents.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe

* Keep query visitor changes limited to JSON conversion

Remove incidental formatter changes outside the JSON containment guard.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe

* Keep timetz JSON formatting culture-invariant

Replace the obsolete SQL execution API in the JSON regression fixture.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe

* Match ZonedDateTime JSON query precision to parameter encoding

Truncate timestamp extraction toward the PostgreSQL epoch while retaining nanosecond precision in stored JSON. Cover scalar, recordset, and primitive collection queries before and after the epoch.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe

* Apply ZonedDateTime JSON precision after epoch normalization

Compare reduced-precision JSON scalar, recordset and collection extraction to native columns, while preserving full-precision JSON round trips.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe

* Preserve existing JSON formats in date/time mapping fixes

Fix ZonedDateTime deserialization by reading the offset already stored in JSON, without changing its writer or precision. Remove the zone-bearing format and all associated query conversion infrastructure. Keep whole-hour timetz text unchanged while retaining fractional offset minutes.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d486c791-406a-414a-b5d3-f4a3716c33fe
Assets 2
Loading