diff options
| author | Andrew Dunstan <andrew@dunslane.net> | 2015-02-26 12:25:21 -0500 |
|---|---|---|
| committer | Andrew Dunstan <andrew@dunslane.net> | 2015-02-26 12:25:21 -0500 |
| commit | bda76c1c8cfb1d11751ba6be88f0242850481733 (patch) | |
| tree | de3272dade43151c7f9668e18cb8111f2da70bb6 /src/backend/commands | |
| parent | fd6a3f3ad4067f1b8fc28e9de6e99e5936d82161 (diff) | |
| download | postgresql-bda76c1c8cfb1d11751ba6be88f0242850481733.tar.gz postgresql-bda76c1c8cfb1d11751ba6be88f0242850481733.zip | |
Render infinite date/timestamps as 'infinity' for json/jsonb
Commit ab14a73a6c raised an error in these cases and later the
behaviour was copied to jsonb. This is what the XML code, which we
then adopted, does, as the XSD types don't accept infinite values.
However, json dates and timestamps are just strings as far as json is
concerned, so there is no reason not to render these values as
'infinity'.
The json portion of this is backpatched to 9.4 where the behaviour was
introduced. The jsonb portion only affects the development branch.
Per gripe on pgsql-general.
Diffstat (limited to 'src/backend/commands')
0 files changed, 0 insertions, 0 deletions