diff options
| author | Peter Eisentraut | 2023-08-18 05:41:14 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2023-08-18 05:41:14 +0000 |
| commit | 881cd9e581c2c40023f82edcd1cd2335691b78f2 (patch) | |
| tree | ab1a8f7cf31793f75e72be99e40ebd79b30a0602 /src/test/regress | |
| parent | 249d74394500e0830d45769423fe8aac7012537c (diff) | |
Remove dubious warning message from SQL/JSON functions
There was a warning that FORMAT JSON has no effect on json/jsonb
types, which is true, but it's not clear why we should issue a warning
about it. The SQL standard does not say anything about this, which
should generally govern the behavior here. So remove it.
Discussion: https://www.postgresql.org/message-id/flat/dfec2cae-d17e-c508-6d16-c2dba82db486%40eisentraut.org
Diffstat (limited to 'src/test/regress')
| -rw-r--r-- | src/test/regress/expected/sqljson.out | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/src/test/regress/expected/sqljson.out b/src/test/regress/expected/sqljson.out index e654c948047..5e7da96be5e 100644 --- a/src/test/regress/expected/sqljson.out +++ b/src/test/regress/expected/sqljson.out @@ -374,9 +374,6 @@ ERROR: JSON ENCODING clause is only allowed for bytea input type LINE 1: SELECT JSON_OBJECT('foo': NULL::int FORMAT JSON ENCODING UTF... ^ SELECT JSON_OBJECT('foo': NULL::json FORMAT JSON); -WARNING: FORMAT JSON has no effect for json and jsonb types -LINE 1: SELECT JSON_OBJECT('foo': NULL::json FORMAT JSON); - ^ json_object ---------------- {"foo" : null} @@ -387,9 +384,6 @@ ERROR: JSON ENCODING clause is only allowed for bytea input type LINE 1: SELECT JSON_OBJECT('foo': NULL::json FORMAT JSON ENCODING UT... ^ SELECT JSON_OBJECT('foo': NULL::jsonb FORMAT JSON); -WARNING: FORMAT JSON has no effect for json and jsonb types -LINE 1: SELECT JSON_OBJECT('foo': NULL::jsonb FORMAT JSON); - ^ json_object --------------- {"foo": null} |