| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Automatic deletion of orphaned rows |
| Date: | 2025-01-22 15:15:04 |
| Message-ID: | CANzqJaBvJ=jXKuyahznN3_GrT0gAdw+r_+xSOd7P72EVufMvSw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 22, 2025 at 9:37 AM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wednesday, January 22, 2025, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
> wrote:
>>
>>
>>> I therefore propose a feature, to be able to specify in a table schema
>>> that a row should be deleted if orphaned.
>>
>>
>> For one thing, rows *can't* be orphaned if there's a foreign key
>> reference.
>>
>
> The description was correct even though using probably imprecise
> terminology. The basic goal is to delete childless parents.
>
That's kinda what I thought he wrote, but it's so far beyond "normal" that
I dismissed the possibility. Parents are allowed to not have
children, after all.
Is there *ANY* DBMS with a built-in reverse FK "parents must have children"
feature?
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Brindusa | 2025-01-22 17:33:37 | Return of the pg_wal issue.. |
| Previous Message | Greg Sabino Mullane | 2025-01-22 15:11:26 | Re: Automatic deletion of orphaned rows |