| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Anthony Apollis <anthony(dot)apollis(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unique Primary Key Linked to Multiple Accounts |
| Date: | 2023-11-13 07:22:54 |
| Message-ID: | CAKFQuwZWNG9xavLTb_sJCLO3FUiV+w3Dgbk8cabd2GxWMFbPVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Monday, November 13, 2023, Anthony Apollis <anthony(dot)apollis(at)gmail(dot)com>
wrote:
>
> Please advice.
>
The subset of data you’ve chosen to show does not allow one to draw any
conclusions. Look for the things that are different in the joined result -
the things that are identical are mostly uninteresting when trying to
figure out what additional join conditions are needed so that only a single
matching row is found.
Your other table doesn’t have a primary key defined. If you do that the
answer will likely present itself to you.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2023-11-13 14:42:31 | Re: Properly handle OOM death? |
| Previous Message | Anthony Apollis | 2023-11-13 07:02:41 | Unique Primary Key Linked to Multiple Accounts |