2018-04-03 15:47:18 +02:00
|
|
|
CREATE EXTENSION jsonb_plperl CASCADE;
|
|
|
|
|
|
|
|
|
|
|
|
CREATE FUNCTION testHVToJsonb() RETURNS jsonb
|
|
|
|
LANGUAGE plperl
|
|
|
|
TRANSFORM FOR TYPE jsonb
|
|
|
|
AS $$
|
|
|
|
$val = {a => 1, b => 'boo', c => undef};
|
|
|
|
return $val;
|
|
|
|
$$;
|
|
|
|
|
|
|
|
SELECT testHVToJsonb();
|
|
|
|
|
|
|
|
|
|
|
|
CREATE FUNCTION testAVToJsonb() RETURNS jsonb
|
|
|
|
LANGUAGE plperl
|
|
|
|
TRANSFORM FOR TYPE jsonb
|
|
|
|
AS $$
|
|
|
|
$val = [{a => 1, b => 'boo', c => undef}, {d => 2}];
|
|
|
|
return $val;
|
|
|
|
$$;
|
|
|
|
|
|
|
|
SELECT testAVToJsonb();
|
|
|
|
|
|
|
|
|
|
|
|
CREATE FUNCTION testSVToJsonb() RETURNS jsonb
|
|
|
|
LANGUAGE plperl
|
|
|
|
TRANSFORM FOR TYPE jsonb
|
|
|
|
AS $$
|
|
|
|
$val = 1;
|
|
|
|
return $val;
|
|
|
|
$$;
|
|
|
|
|
|
|
|
SELECT testSVToJsonb();
|
|
|
|
|
|
|
|
|
2018-04-30 18:28:45 +02:00
|
|
|
CREATE FUNCTION testInf() RETURNS jsonb
|
|
|
|
LANGUAGE plperl
|
|
|
|
TRANSFORM FOR TYPE jsonb
|
|
|
|
AS $$
|
2018-05-01 05:58:48 +02:00
|
|
|
$val = 9**9**9; # we assume this will overflow to +Inf
|
2018-04-30 18:28:45 +02:00
|
|
|
return $val;
|
|
|
|
$$;
|
|
|
|
|
|
|
|
SELECT testInf();
|
|
|
|
|
|
|
|
|
|
|
|
CREATE FUNCTION testNaN() RETURNS jsonb
|
|
|
|
LANGUAGE plperl
|
|
|
|
TRANSFORM FOR TYPE jsonb
|
|
|
|
AS $$
|
2018-05-01 05:58:48 +02:00
|
|
|
$val = sin(9**9**9); # we assume sin(inf) will yield NaN
|
2018-04-30 18:28:45 +02:00
|
|
|
return $val;
|
|
|
|
$$;
|
|
|
|
|
|
|
|
SELECT testNaN();
|
|
|
|
|
|
|
|
|
Fix platform and Perl-version dependencies in new jsonb_plperl code.
Testing SvTYPE() directly is more fraught with problems than one might
think, because depending on context Perl might be storing a scalar value
in one of several forms, eg both numeric and string values. This resulted
in Perl-version-dependent buildfarm test failures. Instead use the SvTYPE
test only to distinguish non-scalar cases (AV, HV, NULL). Disambiguate
scalars by testing SvIOK, SvNOK, then SvPOK. This creates a preference
order for how we will resolve cases where the value is available in more
than one form, which seems fine to me.
Furthermore, because we're now dealing directly with a "double" value
in the SvNOK case, we can get rid of an inadequate and unportable
string-comparison test for infinities, and use isinf() instead.
(We do need some additional #include and "-lm" infrastructure to use
that in a contrib module, per prior experiences.)
In passing, prevent the regression test results from depending on DROP
CASCADE order; I've not seen that malfunction, but it's trouble waiting
to happen.
Discussion: https://postgr.es/m/E1f3MMJ-0006bf-B0@gemulon.postgresql.org
2018-04-04 17:28:33 +02:00
|
|
|
-- this revealed a bug in the original implementation
|
|
|
|
CREATE FUNCTION testRegexpResultToJsonb() RETURNS jsonb
|
|
|
|
LANGUAGE plperl
|
|
|
|
TRANSFORM FOR TYPE jsonb
|
|
|
|
AS $$
|
|
|
|
return ('1' =~ m(0\t2));
|
|
|
|
$$;
|
|
|
|
|
|
|
|
SELECT testRegexpResultToJsonb();
|
|
|
|
|
|
|
|
|
2018-04-03 15:47:18 +02:00
|
|
|
CREATE FUNCTION roundtrip(val jsonb) RETURNS jsonb
|
|
|
|
LANGUAGE plperl
|
|
|
|
TRANSFORM FOR TYPE jsonb
|
|
|
|
AS $$
|
|
|
|
return $_[0];
|
|
|
|
$$;
|
|
|
|
|
|
|
|
|
|
|
|
SELECT roundtrip('null');
|
|
|
|
SELECT roundtrip('1');
|
|
|
|
SELECT roundtrip('1E+131071');
|
|
|
|
SELECT roundtrip('-1');
|
|
|
|
SELECT roundtrip('1.2');
|
|
|
|
SELECT roundtrip('-1.2');
|
|
|
|
SELECT roundtrip('"string"');
|
|
|
|
SELECT roundtrip('"NaN"');
|
|
|
|
|
|
|
|
SELECT roundtrip('true');
|
|
|
|
SELECT roundtrip('false');
|
|
|
|
|
|
|
|
SELECT roundtrip('[]');
|
|
|
|
SELECT roundtrip('[null, null]');
|
|
|
|
SELECT roundtrip('[1, 2, 3]');
|
|
|
|
SELECT roundtrip('[-1, 2, -3]');
|
|
|
|
SELECT roundtrip('[1.2, 2.3, 3.4]');
|
|
|
|
SELECT roundtrip('[-1.2, 2.3, -3.4]');
|
|
|
|
SELECT roundtrip('["string1", "string2"]');
|
|
|
|
|
|
|
|
SELECT roundtrip('{}');
|
|
|
|
SELECT roundtrip('{"1": null}');
|
|
|
|
SELECT roundtrip('{"1": 1}');
|
|
|
|
SELECT roundtrip('{"1": -1}');
|
|
|
|
SELECT roundtrip('{"1": 1.1}');
|
|
|
|
SELECT roundtrip('{"1": -1.1}');
|
|
|
|
SELECT roundtrip('{"1": "string1"}');
|
|
|
|
|
|
|
|
SELECT roundtrip('{"1": {"2": [3, 4, 5]}, "2": 3}');
|
|
|
|
|
|
|
|
|
Fix platform and Perl-version dependencies in new jsonb_plperl code.
Testing SvTYPE() directly is more fraught with problems than one might
think, because depending on context Perl might be storing a scalar value
in one of several forms, eg both numeric and string values. This resulted
in Perl-version-dependent buildfarm test failures. Instead use the SvTYPE
test only to distinguish non-scalar cases (AV, HV, NULL). Disambiguate
scalars by testing SvIOK, SvNOK, then SvPOK. This creates a preference
order for how we will resolve cases where the value is available in more
than one form, which seems fine to me.
Furthermore, because we're now dealing directly with a "double" value
in the SvNOK case, we can get rid of an inadequate and unportable
string-comparison test for infinities, and use isinf() instead.
(We do need some additional #include and "-lm" infrastructure to use
that in a contrib module, per prior experiences.)
In passing, prevent the regression test results from depending on DROP
CASCADE order; I've not seen that malfunction, but it's trouble waiting
to happen.
Discussion: https://postgr.es/m/E1f3MMJ-0006bf-B0@gemulon.postgresql.org
2018-04-04 17:28:33 +02:00
|
|
|
\set VERBOSITY terse \\ -- suppress cascade details
|
2018-04-03 15:47:18 +02:00
|
|
|
DROP EXTENSION plperl CASCADE;
|