| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(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 |
| Date: | 2008-09-23 03:54:58 |
| Message-ID: | 17129.1222142098@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
... 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))
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-09-23 04:05:59 | Re: hash index improving v3 |
| Previous Message | Alex Hunsaker | 2008-09-23 03:43:14 | Re: hash index improving v3 |