Oh... Thanks. What a lame I'm.
Best Regards,
On Wed, May 5, 2010 at 1:25 AM, Tom Lane wrote:
> Andre Lopes writes:
> > Thanks for the reply. I have not call it STRICT...
>
> Yes you are:
>
> > RETURNS NULL ON NULL INPUT
>
> regards, tom lane
>
Andre Lopes writes:
> Thanks for the reply. I have not call it STRICT...
Yes you are:
> RETURNS NULL ON NULL INPUT
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
Hi,
Thanks for the reply. I have not call it STRICT...
The function is:
[code]
CREATE OR REPLACE FUNCTION "apr_insert_hist_2_1" (IN pNOME_VIEW varchar, IN
pCHAVE_1 varchar, IN pVAL_CHAVE_1 varchar, IN pVAL_CHAVE_2 date, IN
pVAL_CAMPO1 date, IN pVAL_COMENT varchar)
RETURNS void AS
$BODY$
DEC
Andre Lopes writes:
> If I use NULL in any parameter the function does not RAISE any NOTICE. I
> can't pass NULL values in parameters?
Sure you can. Maybe you declared the function STRICT? That means to
not call it for a NULL.
regards, tom lane
--
Sent via pgsql-gener
Hi,
I have a function, that I'm debugging...
If I use NULL in any parameter the function does not RAISE any NOTICE. I
can't pass NULL values in parameters?
[code]
select apr_ins_gder_2_1
('table_fgh' /* Varchar */,
'id_fgh' /* Varchar */,
'5' /* Varchar */,
NULL /* Date */,
'2001-01-05' /* Date
