1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
|
<sql-statement>
--
-- encoding-sensitive tests for json and jsonb
--
SELECT getdatabaseencoding(); -- just to label the results files
</sql-statement>
<sql-statement>
-- first json
-- basic unicode input
SELECT '"\u"'::json; -- ERROR, incomplete escape
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
-- first json
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: "\u" must be followed by four hexadecimal digits.
CONTEXT: JSON data, line 1: "\u"
-- first json
^
<sql-statement>
SELECT '"\u00"'::json; -- ERROR, incomplete escape
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '"\u00"'::json; -- ERROR, incomplete escape
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: "\u" must be followed by four hexadecimal digits.
CONTEXT: JSON data, line 1: "\u00"
SELECT '"\u00"'::json; -- ERROR, incomplete escape
^
<sql-statement>
SELECT '"\u000g"'::json; -- ERROR, g is not a hex digit
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '"\u000g"'::json; -- ERROR, g is not a hex digit
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: "\u" must be followed by four hexadecimal digits.
CONTEXT: JSON data, line 1: "\u000g...
SELECT '"\u000g"'::json; -- ERROR, g is not a hex digit
^
<sql-statement>
SELECT '"\u0000"'::json; -- OK, legal escape
</sql-statement>
<sql-statement>
SELECT '"\uaBcD"'::json; -- OK, uppercase and lower case both OK
</sql-statement>
<sql-statement>
-- handling of unicode surrogate pairs
select json '{ "a": "\ud83d\ude04\ud83d\udc36" }' -> 'a' as correct_in_utf8;
</sql-statement>
<sql-statement>
select json '{ "a": "\ud83d\ud83d" }' -> 'a'; -- 2 high surrogates in a row
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
select json '{ "a": "\ud83d\ud83d" }' -> 'a'; -- 2 high surrogates in a row
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: Unicode high surrogate must not follow a high surrogate.
CONTEXT: JSON data, line 1: { "a":...
select json '{ "a": "\ud83d\ud83d" }' -> 'a'; -- 2 high surrogates in a row
^
<sql-statement>
select json '{ "a": "\ude04\ud83d" }' -> 'a'; -- surrogates in wrong order
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
select json '{ "a": "\ude04\ud83d" }' -> 'a'; -- surrogates in wrong order
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: Unicode low surrogate must follow a high surrogate.
CONTEXT: JSON data, line 1: { "a":...
select json '{ "a": "\ude04\ud83d" }' -> 'a'; -- surrogates in wrong order
^
<sql-statement>
select json '{ "a": "\ud83dX" }' -> 'a'; -- orphan high surrogate
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
select json '{ "a": "\ud83dX" }' -> 'a'; -- orphan high surrogate
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: Unicode low surrogate must follow a high surrogate.
CONTEXT: JSON data, line 1: { "a":...
select json '{ "a": "\ud83dX" }' -> 'a'; -- orphan high surrogate
^
<sql-statement>
select json '{ "a": "\ude04X" }' -> 'a'; -- orphan low surrogate
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
select json '{ "a": "\ude04X" }' -> 'a'; -- orphan low surrogate
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: Unicode low surrogate must follow a high surrogate.
CONTEXT: JSON data, line 1: { "a":...
select json '{ "a": "\ude04X" }' -> 'a'; -- orphan low surrogate
^
<sql-statement>
--handling of simple unicode escapes
select json '{ "a": "the Copyright \u00a9 sign" }' as correct_in_utf8;
</sql-statement>
<sql-statement>
select json '{ "a": "dollar \u0024 character" }' as correct_everywhere;
</sql-statement>
<sql-statement>
select json '{ "a": "dollar \\u0024 character" }' as not_an_escape;
</sql-statement>
<sql-statement>
select json '{ "a": "null \u0000 escape" }' as not_unescaped;
</sql-statement>
<sql-statement>
select json '{ "a": "null \\u0000 escape" }' as not_an_escape;
</sql-statement>
<sql-statement>
select json '{ "a": "the Copyright \u00a9 sign" }' ->> 'a' as correct_in_utf8;
</sql-statement>
<sql-statement>
select json '{ "a": "dollar \u0024 character" }' ->> 'a' as correct_everywhere;
</sql-statement>
<sql-statement>
select json '{ "a": "dollar \\u0024 character" }' ->> 'a' as not_an_escape;
</sql-statement>
<sql-statement>
select json '{ "a": "null \u0000 escape" }' ->> 'a' as fails;
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
select json '{ "a": "null \u0000 escape" }' ->> 'a' as fails;
^
-stdin-:<main>:1:1: Fatal: ERROR: unsupported Unicode escape sequence
DETAIL: \u0000 cannot be converted to text.
CONTEXT: JSON data, line 1: { "a":...
select json '{ "a": "null \u0000 escape" }' ->> 'a' as fails;
^
<sql-statement>
select json '{ "a": "null \\u0000 escape" }' ->> 'a' as not_an_escape;
</sql-statement>
<sql-statement>
-- then jsonb
-- basic unicode input
SELECT '"\u"'::jsonb; -- ERROR, incomplete escape
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
-- then jsonb
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: "\u" must be followed by four hexadecimal digits.
CONTEXT: JSON data, line 1: "\u"
-- then jsonb
^
<sql-statement>
SELECT '"\u00"'::jsonb; -- ERROR, incomplete escape
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '"\u00"'::jsonb; -- ERROR, incomplete escape
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: "\u" must be followed by four hexadecimal digits.
CONTEXT: JSON data, line 1: "\u00"
SELECT '"\u00"'::jsonb; -- ERROR, incomplete escape
^
<sql-statement>
SELECT '"\u000g"'::jsonb; -- ERROR, g is not a hex digit
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '"\u000g"'::jsonb; -- ERROR, g is not a hex digit
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: "\u" must be followed by four hexadecimal digits.
CONTEXT: JSON data, line 1: "\u000g...
SELECT '"\u000g"'::jsonb; -- ERROR, g is not a hex digit
^
<sql-statement>
SELECT '"\u0045"'::jsonb; -- OK, legal escape
</sql-statement>
<sql-statement>
SELECT '"\u0000"'::jsonb; -- ERROR, we don't support U+0000
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT '"\u0000"'::jsonb; -- ERROR, we don't support U+0000
^
-stdin-:<main>:1:1: Fatal: ERROR: unsupported Unicode escape sequence
DETAIL: \u0000 cannot be converted to text.
CONTEXT: JSON data, line 1: ...
SELECT '"\u0000"'::jsonb; -- ERROR, we don't support U+0000
^
<sql-statement>
-- use octet_length here so we don't get an odd unicode char in the
-- output
SELECT octet_length('"\uaBcD"'::jsonb::text); -- OK, uppercase and lower case both OK
</sql-statement>
<sql-statement>
-- handling of unicode surrogate pairs
SELECT octet_length((jsonb '{ "a": "\ud83d\ude04\ud83d\udc36" }' -> 'a')::text) AS correct_in_utf8;
</sql-statement>
<sql-statement>
SELECT jsonb '{ "a": "\ud83d\ud83d" }' -> 'a'; -- 2 high surrogates in a row
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT jsonb '{ "a": "\ud83d\ud83d" }' -> 'a'; -- 2 high surrogates in a row
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: Unicode high surrogate must not follow a high surrogate.
CONTEXT: JSON data, line 1: { "a":...
SELECT jsonb '{ "a": "\ud83d\ud83d" }' -> 'a'; -- 2 high surrogates in a row
^
<sql-statement>
SELECT jsonb '{ "a": "\ude04\ud83d" }' -> 'a'; -- surrogates in wrong order
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT jsonb '{ "a": "\ude04\ud83d" }' -> 'a'; -- surrogates in wrong order
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: Unicode low surrogate must follow a high surrogate.
CONTEXT: JSON data, line 1: { "a":...
SELECT jsonb '{ "a": "\ude04\ud83d" }' -> 'a'; -- surrogates in wrong order
^
<sql-statement>
SELECT jsonb '{ "a": "\ud83dX" }' -> 'a'; -- orphan high surrogate
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT jsonb '{ "a": "\ud83dX" }' -> 'a'; -- orphan high surrogate
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: Unicode low surrogate must follow a high surrogate.
CONTEXT: JSON data, line 1: { "a":...
SELECT jsonb '{ "a": "\ud83dX" }' -> 'a'; -- orphan high surrogate
^
<sql-statement>
SELECT jsonb '{ "a": "\ude04X" }' -> 'a'; -- orphan low surrogate
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT jsonb '{ "a": "\ude04X" }' -> 'a'; -- orphan low surrogate
^
-stdin-:<main>:1:1: Fatal: ERROR: invalid input syntax for type json
DETAIL: Unicode low surrogate must follow a high surrogate.
CONTEXT: JSON data, line 1: { "a":...
SELECT jsonb '{ "a": "\ude04X" }' -> 'a'; -- orphan low surrogate
^
<sql-statement>
-- handling of simple unicode escapes
SELECT jsonb '{ "a": "the Copyright \u00a9 sign" }' as correct_in_utf8;
</sql-statement>
<sql-statement>
SELECT jsonb '{ "a": "dollar \u0024 character" }' as correct_everywhere;
</sql-statement>
<sql-statement>
SELECT jsonb '{ "a": "dollar \\u0024 character" }' as not_an_escape;
</sql-statement>
<sql-statement>
SELECT jsonb '{ "a": "null \u0000 escape" }' as fails;
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT jsonb '{ "a": "null \u0000 escape" }' as fails;
^
-stdin-:<main>:1:1: Fatal: ERROR: unsupported Unicode escape sequence
DETAIL: \u0000 cannot be converted to text.
CONTEXT: JSON data, line 1: { "a":...
SELECT jsonb '{ "a": "null \u0000 escape" }' as fails;
^
<sql-statement>
SELECT jsonb '{ "a": "null \\u0000 escape" }' as not_an_escape;
</sql-statement>
<sql-statement>
SELECT jsonb '{ "a": "the Copyright \u00a9 sign" }' ->> 'a' as correct_in_utf8;
</sql-statement>
<sql-statement>
SELECT jsonb '{ "a": "dollar \u0024 character" }' ->> 'a' as correct_everywhere;
</sql-statement>
<sql-statement>
SELECT jsonb '{ "a": "dollar \\u0024 character" }' ->> 'a' as not_an_escape;
</sql-statement>
<sql-statement>
SELECT jsonb '{ "a": "null \u0000 escape" }' ->> 'a' as fails;
</sql-statement>
-stdin-:<main>: Fatal: Execution
-stdin-:<main>:1:1: Fatal: Execution of node: Result
SELECT jsonb '{ "a": "null \u0000 escape" }' ->> 'a' as fails;
^
-stdin-:<main>:1:1: Fatal: ERROR: unsupported Unicode escape sequence
DETAIL: \u0000 cannot be converted to text.
CONTEXT: JSON data, line 1: { "a":...
SELECT jsonb '{ "a": "null \u0000 escape" }' ->> 'a' as fails;
^
<sql-statement>
SELECT jsonb '{ "a": "null \\u0000 escape" }' ->> 'a' as not_an_escape;
</sql-statement>
|
