Skip site navigation (1) Skip section navigation (2)

Re: passing values to a function

From: Jan Wieck <janwieck(at)Yahoo(dot)com>
To: Cedar Cox <cedarc(at)visionforisrael(dot)com>
Cc: Jan Wieck <janwieck(at)yahoo(dot)com>, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: passing values to a function
Date: 2001-02-20 09:19:52
Message-ID: 200102200919.EAA02976@jupiter.jw.home (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
Cedar Cox wrote:
> Giving
>   select update_sentitems('INSERT',1);
> returns
>   NOTICE:   varop = INSERT
> as expected, however if you give
>   select update_sentitems('INSERT',null);
> this is returned:
>   NOTICE:   varop = <NULL>
> BTW, it doesn't matter if both parameters are text or int4.  Also, it
> doesn't matter which one is given as null, they both turn up null.
> Bottom line seems to be that if you call the function with any parameter
> null, they are all null.  Sooo.. what's up here?  Is this a bug that's
> been fixed in 7.0.3? (I'm still using 7.0.2).

    I  wouldn't call it a bug, it was a lack of capabilities with
    the pre7.1 function manager. It had only one flag for NULL to
    pass  to  the  function,  so  it said "there is a NULL, but I
    don't tell you which arg it is".

    7.1 is the first that does it correct.



# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck(at)Yahoo(dot)com #

Do You Yahoo!?
Get your free address at

In response to


pgsql-interfaces by date

Next:From: Ramachandra K.B.SDate: 2001-02-20 09:24:22
Subject: RE: [JDBC] Re: First-time JDBC setup with Jakarta! Whee!
Previous:From: Peter T MountDate: 2001-02-20 08:48:51
Subject: Re: First-time JDBC setup with Jakarta! Whee!

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group