| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Peter Moser <pitiz29a(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Johann Gamper <gamper(at)inf(dot)unibz(dot)it>, Michael Böhlen <boehlen(at)ifi(dot)uzh(dot)ch>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Anton Dignös <anton(dot)dignoes(at)unibz(dot)it> |
| Subject: | Re: [PROPOSAL] Temporal query processing with range types |
| Date: | 2017-02-24 20:25:34 |
| Message-ID: | 274d854f-a9be-bc65-691a-5c93516fd896@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/24/17 6:40 AM, Peter Moser wrote:
> Do you think it is better to remove the syntax for ranges expressed in
> different columns?
It's not that hard to construct a range type on-the-fly from 2 columns,
so (without having looked at the patch or really followed the thread) I
would think the answer is yes.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Flower | 2017-02-24 20:25:55 | Re: case_preservation_and_insensitivity = on |
| Previous Message | Jim Nasby | 2017-02-24 20:23:52 | Re: bytea_output output of base64 |