| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: RangeTypes |
| Date: | 2011-01-28 18:29:03 |
| Message-ID: | 22773.1296239343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Fri, 2011-01-28 at 09:17 -0800, David Fetter wrote:
>> For consistency, and in order not to continue our atrocious naming
>> tradition, I'd like to propose that the above be named timestamprange
>> (tsrange for short) and timestamptzrange (tstzrange for short).
> No real objection, but I'd like to see if someone else will second it.
> Also, I don't think aliases are very easy to define.
They are not, and should be avoided. I don't think we have *any*
typename aliases except for cases required by SQL standard.
>> Should there also be a timerange and a timetzrange?
> I thought about it, and I realized that I've never seen the "time" type
> used. Again, I'll add it if someone will use it.
I have no idea what the semantics of timetzrange would be. Even
timerange would be a bit funny --- is 11PM before or after 1AM?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-28 18:36:45 | Re: FPI |
| Previous Message | Jeff Davis | 2011-01-28 17:48:52 | Re: WIP: RangeTypes |