Re: [HACKERS] Re: [BUGS] Unnexpected results using to_number()

2000-07-12 Thread Karel Zak
On Sun, 9 Jul 2000, Tom Lane wrote: > "Andrew Snow" <[EMAIL PROTECTED]> writes: > > # SELECT to_number('12,454.8-', ''); > > pqReadData() -- backend closed the channel unexpectedly. > > In current sources I get a NULL result, which seems to be what the > code author intended originally. However

Re: [HACKERS] Re: [BUGS] Unnexpected results using to_number()

2000-07-09 Thread Tom Lane
Karel Zak <[EMAIL PROTECTED]> writes: > On Sun, 9 Jul 2000, Tom Lane wrote: >> "Andrew Snow" <[EMAIL PROTECTED]> writes: # SELECT to_number('12,454.8-', ''); pqReadData() -- backend closed the channel unexpectedly. >> >> In current sources I get a NULL result, which seems to be what the

Re: [BUGS] Unnexpected results using to_number()

2000-07-09 Thread Tom Lane
"Andrew Snow" <[EMAIL PROTECTED]> writes: > # SELECT to_number('12,454.8-', ''); > pqReadData() -- backend closed the channel unexpectedly. In current sources I get a NULL result, which seems to be what the code author intended originally. However this seems a little bit inconsistent --- shouldn

[BUGS] Unnexpected results using to_number()

2000-07-08 Thread Andrew Snow
Is this supposed to happen? I discovered this when I was experimenting with converting a string to a number. # SELECT to_number('12,454.8-', '99G999D9S'); to_number --- -12454.8 (1 row) # SELECT to_number('12,454.8-', ''); pqReadData() -- backend closed the channel unexpectedly.