> So here are my questions:See link for question #3; namely use the three-arg version of daterange
>
> 1) Is there anyway to control this behavior of daterange(), or is it just
> best to (for example) add 1 to the upper bound argument if I want an
> inclusive upper bound?
(type,type,text)
Not easily - you could write a custom type with the desired canonical form.
> 2) This is purely cosmetic, but is there anyway to control the output
> formatting of a daterange to show the upper bound as inclusive? So that
> daterange(d1,d2) would display as [d1,d2-1] rather than [d1,d2)?
Yes, the documentation could maybe use some work on this topic. The
> 3) I couldn't find this discussed in the documentation, and specifically
> didn't find the daterange() function documented, including on this page
> where I might have expected it:
> http://www.postgresql.org/docs/9.3/static/functions-range.html. Is it
> somewhere else where I'm not finding it?
relevant information is provided at:
http://www.postgresql.org/docs/9.3/interactive/rangetypes.html
See especially: 8.17.2 & 8.17.6
David J.
Thanks for your help!
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Questions-about-daterange-function-tp5809274p5809277.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
AGENCY Software
A Free Software data system
By and for non-profits
(253) 245-3801
learn more about AGENCY or
follow the discussion.
