The README's Type Coverage and Examples sections show working SQL for:
hilbert_encodehilbert_decodemorton_encode
…but morton_decode is described in the parameter list without a corresponding usage example. That's the only one of the four that doesn't have a runnable round-trip snippet in the docs.
For symmetry — and so users picking Morton over Hilbert have a clear cookbook entry — would be good to add a snippet alongside the existing Hilbert decode, e.g.:
SELECT morton_decode(
morton_encode([10, 20]::INTEGER[2]),
/* num_elements */ 2,
/* return_float */ false,
/* return_unsigned */ true
) AS roundtrip;
-- [10, 20]
Surfaced this while running an automated coverage report over our docs site — morton_decode was the only function in the introspected surface that had no example in either the upstream README or anywhere downstream. Trivial fix, just flagging.
The README's Type Coverage and Examples sections show working SQL for:
hilbert_encodehilbert_decodemorton_encode…but
morton_decodeis described in the parameter list without a corresponding usage example. That's the only one of the four that doesn't have a runnable round-trip snippet in the docs.For symmetry — and so users picking Morton over Hilbert have a clear cookbook entry — would be good to add a snippet alongside the existing Hilbert decode, e.g.:
Surfaced this while running an automated coverage report over our docs site —
morton_decodewas the only function in the introspected surface that had no example in either the upstream README or anywhere downstream. Trivial fix, just flagging.