From: | Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il> |
---|---|
To: | Sebestyen Zoltan <szoli(at)netvisor(dot)hu>, PostgreSQL general mailinglist <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: [GENERAL] Unexpected input in plpgsql script. |
Date: | 1999-02-03 12:17:27 |
Message-ID: | l03110703b2ddeeb3999d@[147.233.159.109] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 22:15 +0200 on 02/02/1999, Sebestyen Zoltan wrote:
> sum
> ---
>
> (1 row)
>
> I.e. there's a row containing NOTHING. I wrote a number formatter script
> with a help of this list which works beautifully except for this case. In
> this case I've got the following message:
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally before or
> while processing the request. We have lost the connection to the backend,
> so further processing is impossible.
> Terminating.
>
> How can I handle such a case in a plpgsql function or how could I avoid
> it?
Can't you simply test whether the returned value IS NULL or not?
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma
From | Date | Subject | |
---|---|---|---|
Next Message | jose' soares | 1999-02-03 14:42:25 | Re: [GENERAL] Unexpected input in plpgsql script. |
Previous Message | Bruce Momjian | 1999-02-03 03:57:01 | Re: [GENERAL] Cost: Big Tables vs. Organized Separation of Data |