Re: [HACKERS] [PROPOSAL] Temporal query processing with range types - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] [PROPOSAL] Temporal query processing with range types
Date
Msg-id 274d854f-a9be-bc65-691a-5c93516fd896@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] [PROPOSAL] Temporal query processing with range types  (Peter Moser <pitiz29a@gmail.com>)
Responses Re: [HACKERS] [PROPOSAL] Temporal query processing with range types  (Peter Moser <pitiz29a@gmail.com>)
List 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)



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] bytea_output output of base64
Next
From: Gavin Flower
Date:
Subject: Re: [HACKERS] case_preservation_and_insensitivity = on