Bruce, This function which has even more errors also raises no errors when run in the query editor: CREATE or replace function annual.get_ratio72( float8, float8) RETURNS pg_catalog.float8 AS $BODY$ DECLARE execptioncount_in alias for $1; questioncount_in alias for $2; IF (execptioncount_in >0) AND (questioncount_in >0) --THEN RATIO_OUT = execptioncount_in / questioncount_in; ELSE --this variable is not declared, yet when I run this query no error is raised EXCEPTIONRATIO_OUT = 0; END; return ratio_out; END; $BODY$ LANGUAGE 'plpgsql' VOLATILE; > From: Bruce Momjian <pgman@xxxxxxxxxxxxxxxx> > Date: 2005/02/21 Mon AM 10:47:35 EST > To: tony_caduto@xxxxxxxxxxxxxxxxxxxx > CC: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: is there anyway to get the backends IP address from > > Tony Caduto wrote: > > Bruce, > > On another note, is there plans to improve the type checking of stored > > functions during the save/compile? > > Currently I can pretty much make tons of mistakes (on purpose of course > > :-) and they are not flagged as errors until runtime. > > The biggest complaint I see from other DBAs (MS SQL, Oracle) is that > > Postgres does little to no pre-runtime type checking. > > We have no plans to improve that. We do have 'check_function_bodies' > which defaults to true and does some checking. Would you give us a > particular example you would like improved? > > -- > Bruce Momjian | http://candle.pha.pa.us > pgman@xxxxxxxxxxxxxxxx | (610) 359-1001 > + If your life is a hard drive, | 13 Roberts Road > + Christ can be your backup. | Newtown Square, Pennsylvania 19073 > ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings