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 18:47:21 |
Message-ID: | alpine.LNX.2.20.1901171043301.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:
> It would produce results, so yes it would work. The question are they the
> results you want?
Adrian,
To which the answer is no as I just discovered.
> The above would return anything with a next_contact less then today. That
> could extend backwards to some undetermined point in the past, depending
> on how diligent you where on updating next_contact. Before you go much
> further I would look over the suggestions posted and then sit down with
> pen and paper and figure out what it you want to track and how you are
> going to maintain that tracking. Then draw up an outline of how you will
> achieve that in code.
I have that tracking defined (who is active and needs a contact today or
earlier) and am now working on how to code it so only the last contact for a
person is examined to determine if the active column = true. I'll ponder
that.
Thanks,
Rich
From | Date | Subject | |
---|---|---|---|
Next Message | Ahtesham Karajgi | 2019-01-17 19:59:46 | Need aws_oracle_ext.systimestamp function defination for postgres |
Previous Message | Adrian Klaver | 2019-01-17 18:16:14 | Re: Refining query statement |