Migrating towards Temporal.Duration

[louisboulagnon]

Hello, thank you for your work on this project,

With the standardization of the Temporal API and its inclusion in node 26, would it be worth considering parsing interval results as a Temporal.Duration when available ?

Thankfully, PostgresInterval has a very close shape to Duration, so downstream migration shouldn't be too complicated, but I think using the standard type directly would be useful for interoperability without having to transform the output

There would need to be some coordination with node-postgres for param parsing

[bendrucker]

See #56. Any upgrade in higher level libraries will wait longer for this to reach LTS and really for any version not supporting this to age out of LTS before switching the default in a breaking release. But you can certainly use this in the mean time.

[bendrucker]

The only real hazard I found was the mixed sign durations not being supported. But since the goal here is really parsing Postgres outputs for a given type versus all acceptable input forms, that seems fine/consistent. Let me know if you have any other comments, can release this shortly otherwise.

[louisboulagnon]

Thank you for your quick work on this !

It does make sense to await full LTS support and 24 being EOL before making this breaking change.
The converter is already plenty, and I especially like that the name mirrors the Date.prototype.toTemporalInstant.

Regarding mixed signs, I agree throwing is the only real option