| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Refining query statement |
| Date: | 2019-01-17 16:56:47 |
| Message-ID: | CAKFQuwaTZKOsMK6DpnuwJ4xbHAgiZqNsHBAHmqGED=g0=DW2kg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jan 17, 2019 at 9:47 AM Rich Shepard <rshepard(at)appl-ecosys(dot)com> wrote:
> What I want is a list of contacts to make today. This includes ones that
> should have been made earlier but weren't and excludes earlier contacts that
> have no scheduled next contact (therefore, the nulls.).
>
> Does this clarify what I'm asking of the data?
Yes...though now it just sounds like a flawed data model. How stuck
are you in that regard? Those "future" contacts should have their own
records and not be derived via an optional field on an existing
record.
Put differently, how do you know which activities are completed and
which are not?
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2019-01-17 17:07:06 | Re: Refining query statement |
| Previous Message | Rich Shepard | 2019-01-17 16:50:01 | Re: Refining query statement |