That is certainly clearer - thank you.
On Tue, Oct 4, 2011 at 10:39 PM, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > Here is a doc patch that at least explains the example. Applied.
> >
> > I think s/or/otherwise/ (both places) would make that read better.
>
> Done wi
Tom Lane wrote:
> Bruce Momjian writes:
> > Here is a doc patch that at least explains the example. Applied.
>
> I think s/or/otherwise/ (both places) would make that read better.
Done with the attached patch.
--
Bruce Momjian http://momjian.us
EnterpriseDB
Bruce Momjian writes:
> Here is a doc patch that at least explains the example. Applied.
I think s/or/otherwise/ (both places) would make that read better.
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscri
Alvaro Herrera wrote:
>
> Excerpts from Henry Drexler's message of mi?? sep 21 12:50:18 -0300 2011:
> > 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.
>
> Maybe the fix is just to add a sim
Alvaro Herrera wrote:
>
> Excerpts from Henry Drexler's message of mi?? sep 21 12:50:18 -0300 2011:
> > 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.
>
> Maybe the fix is just to add a sim
Excerpts from Henry Drexler's message of mié sep 21 12:50:18 -0300 2011:
> 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.
Maybe the fix is just to add a simpler example, without altering the
word
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.gritt...@wicourts.gov> wrote:
> Henry Drexler wrote:
>
> > "If the
Henry Drexler 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 o
http://www.postgresql.org/docs/9.1/static/functions-conditional.html
states: "The COALESCE function returns the first of its arguments that is
not null. Null is returned only if all arguments are null."
I was having a terrible time understanding this, and looking at the two
examples were just as
