Re: coalesce

From: Henry Drexler <alonup8tb(at)gmail(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-docs(at)postgresql(dot)org
Subject: Re: coalesce
Date: 2011-09-21 15:50:18
Message-ID: CAAtgU9SkWwHw4cXJ7OgdkHWF8ohGB7ocSFDVBjO22=kH9FLsMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

thanks,

so I take it I am not getting those more complex examples (that are
apparently beyond my use case), I will take a look at them again.

Thank you for the feedback.

On Wed, Sep 21, 2011 at 10:33 AM, Kevin Grittner <
Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:

> Henry Drexler <alonup8tb(at)gmail(dot)com> wrote:
>
> > "If the results of the first argument are null, it will return the
> > second."
>
> Unless the second is also null, in which case it will return the
> third. Unless the third is also null...
>
> The trick is to come up with language which recognizes that there
> can be any number of arguments. Personally, I think the existing
> language does a good job of that, and is pretty clear.
>
> > so I made this example that makes sense:
> >
> > COALESCE(column,substitute value)
>
> Perhaps a two-argument example would be helpful, as long as it
> doesn't mislead people into thinking the construct is limited to two
> arguments.
>
> -Kevin
>

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Alvaro Herrera 2011-09-21 16:37:54 Re: coalesce
Previous Message Kevin Grittner 2011-09-21 14:33:36 Re: coalesce