Re: Adding time to DATE type

Can someone give me a TODO summary for this issue?

[ Charset ISO-8859-1 unsupported, converting... ]
> On Fri, 17 Mar 2000, Bruce Momjian wrote:
>
> > test=> SELECT date('1/1/1992') + timespan('1 year');
>
> If I may point something out here, the correct syntax for this in SQL92 is
>
> SELECT DATE '1/1/1992' + INTERVAL '1 year'
>
> (Ignoring the fact that neither the date nor the interval strings have the
> correct format.)
>
> This converts to a cast in PostgreSQL, which is fine, but the standard
> makes a semantic distinction:
>
> CAST('2000-02-29' AS DATE)
>
> converts a character literal to date
>
> DATE '2000-02-29'
>
> *is* a date literal. Furthermore, just
>
> '2000-02-29'
>
> is not a date literal.
>
> I've been doing some lobbying to get rid of the "unknown" type because SQL
> is perfectly clear about what "quote-stuff-quote" means (character type)
> and in absence of any evidence to the contrary (such as a function only
> taking date arguments, inserting it into a date field) it should be
> treated as such. That will get rid of such embarrassments as
>
> SELECT 'a' LIKE 'a' -- try it
>
> Tom believes that this will create a pain for the odd data type crowd but
> I don't think that this is so (or at least has to be so) whereas the
> current behavior creates a pain for the normal data type crowd.
>
> Just my ideas.
>
>
> --
> Peter Eisentraut Sernanders v?g 10:115
> peter_e(at)gmx(dot)net 75262 Uppsala
> http://yi.org/peter-e/ Sweden
>
>

--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026