Re: Refining query statement

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Refining query statement
Date: 2019-01-17 17:37:46
Message-ID: alpine.LNX.2.20.1901170933430.18965@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 17 Jan 2019, Adrian Klaver wrote:

> To be clear the next-activity date = next_contact in the database, correct?

Adrian,

Yes. I've renamed the Activities table to Contacts and the Contacts table
to People.

> NULL basically means unknown, so having it stand for something is a bit of
> a stretch. Seems to me a boolean field of name active to denote contacts
> you need to keep up with is in order. Then make the next_contact field NOT
> NULL and replace the current NULL values with 'infinity':

This makes good sense.

> As to current situation:
>
> 1) Use my previous suggestion.

I did so, but will modify it as you suggest:
> 2) WHERE COALESCE(next_contact, 'infinity') BETWEEN '01/01/2019'::date AND
> 'today'::date

Thanks again,

Rich

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2019-01-17 18:01:09 Re: Refining query statement
Previous Message David G. Johnston 2019-01-17 17:26:23 Re: Refining query statement