Re: Proposed patch: make SQL interval-literal syntax work per spec - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Proposed patch: make SQL interval-literal syntax work per spec
Date
Msg-id 200809231223.m8NCNhV12240@momjian.us
Whole thread Raw
In response to Re: Proposed patch: make SQL interval-literal syntax work per spec  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_type.h regression?
Next
From: Zdenek Kotala
Date:
Subject: Re: Initial prefetch performance testing