Re: [BUGS] select to_number('1,000', '999,999');

2004-11-21 Thread David Schweikert
On Sun, Nov 21, 2004 at 20:10:08 -0500, Tom Lane wrote: > I'm not entirely convinced this is a bug. I get the right answer from > > regression=# select to_number('001,000', '999,999') ; > to_number > --- > 1000 > (1 row) > > It's arguable that to_number() should throw an error wh

Re: [BUGS] select to_number('1,000', '999,999');

2004-11-21 Thread Tom Lane
David Schweikert <[EMAIL PROTECTED]> writes: > select to_number('1,000', '999,999') returns '100'. I'm not entirely convinced this is a bug. I get the right answer from regression=# select to_number('001,000', '999,999') ; to_number --- 1000 (1 row) It's arguable that to_number(

[BUGS] select to_number('1,000', '999,999');

2004-11-21 Thread David Schweikert
POSTGRESQL BUG REPORT TEMPLATE Your name : David Schweikert Your email address : [EMAIL PROTECTED]

pgsql-bugs@postgresql.org

2004-11-21 Thread Michael Fuhr
On Sun, Nov 21, 2004 at 03:16:36AM -0500, Tom Lane wrote: > Michael Fuhr <[EMAIL PROTECTED]> writes: > > If spi_exec_query() fails in a plperl function, subsequent calls > > to plperl or plperlu functions that hadn't been previously loaded > > will fail with "Undefined subroutine &main::mksafefunc"

pgsql-bugs@postgresql.org

2004-11-21 Thread Tom Lane
Michael Fuhr <[EMAIL PROTECTED]> writes: > If spi_exec_query() fails in a plperl function, subsequent calls > to plperl or plperlu functions that hadn't been previously loaded > will fail with "Undefined subroutine &main::mksafefunc". Yeah ... there are other ways to cause this but the short of it