IL PROTECTED]
Subject: Re: [BUGS] comparing null value in plpgsql.
On Mar 10, Stephan Szabo wrote:
> On Mon, 11 Mar 2002, Bhuvan A wrote:
>
> > here i have a problem in comparing null values in plpgsql. this
exist
> > in 7.1.x and 7.2 as well.
> >
> > the conditi
On Mar 10, Stephan Szabo wrote:
> On Mon, 11 Mar 2002, Bhuvan A wrote:
>
> > here i have a problem in comparing null values in plpgsql. this exist
> > in 7.1.x and 7.2 as well.
> >
> > the condition != fails in plpgsql.
> > consider this function is triggered on every updation on a table.
> >
On Mon, 11 Mar 2002, Bhuvan A wrote:
>
>
> On Mar 10, Stephan Szabo wrote:
>
> > On Mon, 11 Mar 2002, Bhuvan A wrote:
> >
> > > here i have a problem in comparing null values in plpgsql. this exist
> > > in 7.1.x and 7.2 as well.
> > >
> > > the condition != fails in plpgsql.
> > > consider th
On Mar 10, Stephan Szabo wrote:
> On Mon, 11 Mar 2002, Bhuvan A wrote:
>
> > here i have a problem in comparing null values in plpgsql. this exist
> > in 7.1.x and 7.2 as well.
> >
> > the condition != fails in plpgsql.
> > consider this function is triggered on every updation on a table.
>
On Mon, 11 Mar 2002, Bhuvan A wrote:
> here i have a problem in comparing null values in plpgsql. this exist
> in 7.1.x and 7.2 as well.
>
> the condition != fails in plpgsql.
> consider this function is triggered on every updation on a table.
>
> create function ftest()
> returns opaque as
hi,
here i have a problem in comparing null values in plpgsql. this exist
in 7.1.x and 7.2 as well.
the condition != fails in plpgsql.
consider this function is triggered on every updation on a table.
create function ftest()
returns opaque as 'declare
begin
if new.comp_code != ol
