| From: | pgsql-bugs(at)postgresql(dot)org |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Bug #915: problem with returning setof with double precision values |
| Date: | 2003-03-21 11:57:47 |
| Message-ID: | 20030321115747.F3869474E4F@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Daniel Brozek (d(dot)brozek(at)adv(dot)pl) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
problem with returning setof with double precision values
Long Description
I have got the table and the function (look at example code). After executing this function I have got NULL values in the place of double precision columns. But in database those values are set. Simple SELECT (select * from service) from this table works propertly - double precision columns have their proper values.
I am working with 7.3.2 version of Postgresql.
Sample Code
CREATE FUNCTION get_krd_info (INTEGER) RETURNS SETOF service AS '
DECLARE
l_service_id ALIAS FOR $1;
l_service service%ROWTYPE;
BEGIN
SELECT INTO l_service service* FROM service
WHERE service.service_id = l_service_id;
RETURN NEXT l_service;
RETURN;
END;
' LANGUAGE 'plpgsql';
No file was uploaded with this report
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-03-21 14:38:05 | Re: alter table |
| Previous Message | DEEPANSHU GARG | 2003-03-21 11:14:07 | Security problem with Postgres sql |