|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: Proposed patch: make SQL interval-literal syntax work per spec|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom, which Interval TODO items did you complete with this patch?
> > http://wiki.postgresql.org/wiki/Todo#Dates_and_Times
> I think we've at least mostly fixed
> * Support ISO INTERVAL syntax if units cannot be determined from the string, and are supplied after the string
> * Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
> There might be a few glitches left but they are at much smaller grain
> than the TODO is talking about.
Thanks, marked as done.
> ... while I'm looking: I am not sure that I think either of these TODO
> items are sane or standards-compliant:
> * Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS INTERVAL MONTH), and this should return '12 months'
> * Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
OK, I have removed the items; we can always re-add them if they are
requested. Thanks for the review.
+ If your life is a hard drive, Christ can be your backup. +
|Next Message||Zdenek Kotala||2008-09-23 12:26:58||Re: Initial prefetch performance testing|
|Previous Message||Tom Lane||2008-09-23 12:16:34||Re: hash index improving v3|