From: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Question about function body checking and 8.1 |
Date: | 2005-03-23 03:04:42 |
Message-ID: | 4240DCCA.8050706@amsoftwaredesign.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ok,
here is a example
CREATE OR REPLACE FUNCTION mytest();
RETURNS VOID as
$$
DECLARE
mytestvar varchar;
mytestvar2 integer;
BEGIN
mytestvarr = 'bla';
select testfield from nonexistanttable where testfield = 2
INTO mytestvar2;
--The table does not exits, yet postgresql does not complain.
END;
$$
LANGUAGE 'plpgsql' VOLATILE;
I also seem to remember that one of the 8.0 betas actually did better
checking, but then it was gone in the next beta. I could be wrong on
that though.
Also if you happen to use PLperl or any of the other ones, do they
actually do better checking than PLpgsql? Last time I used a PLperl
function it didn't do any checking at creation either.
Peter Eisentraut wrote:
>>compatibility or if the SQL statements are valid.
>>
>>
>
>Only for very small values of "no". Please provide an example.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-03-23 03:44:15 | Re: Encoding-related errors when moving from 7.3 to 8.0.1 |
Previous Message | Stephan Szabo | 2005-03-23 02:55:16 | Re: inherited table and rules |