Re: DOMAIN/composite TYPE vs. base TYPE - Mailing list pgsql-general

From Joe Abbate
Subject Re: DOMAIN/composite TYPE vs. base TYPE
Date
Msg-id 20b6c06f-baa5-b6ad-baa7-e3975da9d4de@freedomcircle.com
Whole thread Raw
In response to Re: DOMAIN/composite TYPE vs. base TYPE  ("Gavan Schneider" <list.pg.gavan@pendari.org>)
List 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



pgsql-general by date:

Previous
From: Joe Abbate
Date:
Subject: Re: DOMAIN/composite TYPE vs. base TYPE
Next
From: Adrian Klaver
Date:
Subject: Re: DOMAIN/composite TYPE vs. base TYPE