| From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
|---|---|
| To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Selecting table row with latest date |
| Date: | 2021-08-19 17:25:18 |
| Message-ID: | B0C5781A-21C6-4C0D-B867-25CE8118B466@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Aug 19, 2021, at 11:20 AM, Rich Shepard <rshepard(at)appl-ecosys(dot)com> wrote:
>
> On Thu, 19 Aug 2021, Rob Sargent wrote:
>
>> sorry, wasn’t clear: person_nbr, next_contact
>> On the premise that there can only be one next date.
>
> Rob,
>
> I wasn't sufficiently clear. The contacts table has a row for each
> (person_nbr, contact_date). For each row there's also either a next_contact
> date or that column is null (e.g., pandemic-related no longer at that
> company).
>
Yeah, I get that each person may have been contacted more than once for a history of contacting. I just feel that “next_contact” doesn’t belong there.
> Regards,
>
> Rich
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-08-19 17:38:24 | Re: Selecting table row with latest date |
| Previous Message | Rich Shepard | 2021-08-19 17:20:30 | Re: Selecting table row with latest date |