Re: [BUGS] SELECT '(1, nan, 3)'::cube;

bricklen wrote: > On Tue, Mar 15, 2011 at 9:08 AM, Robert Brewer > wrote: > > I'm working on a hypercube implementation in Postgres using > contrib/cube > > > > and need to insert 80,000 rows in one go from Python. Doing so with > > INSERT, even multiple

[BUGS] SELECT '(1, nan, 3)'::cube

rge numbers to fake the parser into returning Infinity. 2. If anyone can think of a way to trick the cube parser in the short term into returning NaN, I'd love to hear it. 3. If anyone understands cubeparse.c better than I do and can shoot me a quick patch, I'd appreciate it. Robert Brewer fuman...@aminus.org -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] SELECT '(1, nan, 3)'::cube;

Tom Lane wrote: > "Robert Brewer" writes: > > I'm working on a hypercube implementation in Postgres using contrib/cube > > and need to insert 80,000 rows in one go from Python. Doing so with > > INSERT, even multiple statements in one call, is pretty slow. I

[BUGS] SELECT '(1, nan, 3)'::cube;

to fake the parser into returning Infinity. 2. If anyone can think of a way to trick the cube parser in the short term into returning NaN, I'd love to hear it. 3. If anyone understands cubeparse.c better than I do and can shoot me a quick patch, I'd appreciate it. Robert Brewer fuman...@aminus.org -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs