| From: | decibel <decibel(at)decibel(dot)org> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, Scott Bailey <artacus(at)comcast(dot)net>, hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Range types |
| Date: | 2009-12-16 00:03:26 |
| Message-ID: | 69E520B9-18AF-419D-A18D-903E5B94D183@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 15, 2009, at 5:40 PM, Jeff Davis wrote:
> If you think I'm proposing that we drop inclusivity/exclusivity before
> telling the application, that's not what I'm proposing at all. I'm
> proposing that, at least in some circumstances, it's important to be
> able to display the same value in different formats -- e.g. [1, 3) or
> [1, 2], depending on what the application expects. Similar to a timezone
> adjustment.
I think it would help the discussion if you could provide some real examples. I suspect you're thinking of things like scheduling apps, where it's important to be able to do things like "what's the next available time slot?". There are probably ways to make that kind of thing easier without resorting to discrete time.
> [1] "Temporal Data and the Relational Model" by C.J. Date, et al., uses
> discrete time throughout the entire book, aside from a brief discussion
> at the beginning.
I find myself wondering if they were influenced by the technology available at the time...
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | decibel | 2009-12-16 00:06:42 | Re: Range types |
| Previous Message | Josh Berkus | 2009-12-15 23:51:43 | Re: Range types |