Re: coalesce
| От | Henry Drexler |
|---|---|
| Тема | Re: coalesce |
| Дата | |
| Msg-id | CAAtgU9SkWwHw4cXJ7OgdkHWF8ohGB7ocSFDVBjO22=kH9FLsMg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: coalesce ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
| Ответы |
Re: coalesce
|
| Список | 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.Grittner@wicourts.gov> wrote:
Henry Drexler <alonup8tb@gmail.com> wrote:Unless the second is also null, in which case it will return the
> "If the results of the first argument are null, it will return the
> second."
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.Perhaps a two-argument example would be helpful, as long as it
> so I made this example that makes sense:
>
> COALESCE(column,substitute value)
doesn't mislead people into thinking the construct is limited to two
arguments.
-Kevin
В списке pgsql-docs по дате отправления: