Re: DOMAIN/composite TYPE vs. base TYPE

From: Joe Abbate <jma(at)freedomcircle(dot)com>
To: Gavan Schneider <list(dot)pg(dot)gavan(at)pendari(dot)org>
Cc: Rob Sargent <robjsargent(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: DOMAIN/composite TYPE vs. base TYPE
Date: 2020-09-28 22:05:42
Message-ID: 20b6c06f-baa5-b6ad-baa7-e3975da9d4de@freedomcircle.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello Gavan,

On 28/9/20 17:52, Gavan Schneider wrote:
> Consider expressing all the component fields as a range. This allows you
> the ability to be a precise as you need and still have the benefits of
> well defined comparison functions.

I did consider that, but it's a tradeoff between 80% of the cases being
a single precise date, 18% being a single date with some imprecision
around a single month, and the rest with "ranges" of months or other
intervals.

Joe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-09-28 22:12:59 Re: DOMAIN/composite TYPE vs. base TYPE
Previous Message Joe Abbate 2020-09-28 21:58:19 Re: DOMAIN/composite TYPE vs. base TYPE