From: | Roy Badami <roy(at)gnomon(dot)org(dot)uk> |
---|---|
To: | Roy Badami <roy(at)gnomon(dot)org(dot)uk> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1517: SQL interval syntax is accepted by the parser, |
Date: | 2005-03-23 22:37:06 |
Message-ID: | 16961.61330.163465.369750@giles.gnomon.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Roy> The 'constraint' (interval type descriptor or whatever it's
Roy> really called) is mandatory in standard SQL, I think, so
Roy> there's no ambiguity anyway, unless anyone is using this
Roy> undocumented syntax at the moment...
Incidentally, this was the ratinale behind my earlier suggestion, that:
* if the interval type descriptor is absent, parse the interval as a
traditional postgres interval
* if the interval type descriptor is present, parse the interval according
to the standard syntax
I have no objection to allowing things like
'1 hour 10 minutes' DAY TO SECOND
but I'm just wondering whether the hybrid syntax is an unnecessary
complication.
-roy
From | Date | Subject | |
---|---|---|---|
Next Message | Roy Badami | 2005-03-23 22:39:51 | Re: BUG #1517: SQL interval syntax is accepted by the parser, |
Previous Message | Roy Badami | 2005-03-23 22:33:45 | Re: BUG #1517: SQL interval syntax is accepted by the parser, |