BUG #14300: Empty cube representation
The following bug has been logged on the website:
Bug reference: 14300
Logged by: Alexander Ustimenko
Email address: a@ustimen.co
PostgreSQL version: 9.5.4
Operating system: Debian 4.9.2-10 64-bit
Description:
ACTUAL:
SELECT CUBE(ARRAY[]::INTEGER[]);
-- Gives '()'
SELECT '()'::CUBE;
-- Gives 'ERROR: bad cube representation'
SHOULD BE?:
SELECT CUBE(ARRAY[]::INTEGER[]);
-- Should give some 'ERROR: bad cube representation' ?
QUESTION:
Does cube type wrong or cube parser wrong?
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
a@ustimen.co writes:
SELECT CUBE(ARRAY[]::INTEGER[]);
-- Gives '()'
SELECT '()'::CUBE;
-- Gives 'ERROR: bad cube representation'
Hmm. There are more ways than that to produce a cube that cube_in won't
take: you can put in an infinity or NaN coordinate via the cube-from-
float-array path too, and cube_out will print them, but cube_in won't
take them. We fixed something similar with the core geometric types
recently.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs