Skip site navigation (1) Skip section navigation (2)

Re: One more time on ONE-TO-MANY

From: Duane Lee - EGOVX <DLee(at)mail(dot)maricopa(dot)gov>
To: "'Dennis Gearon'" <gearond(at)fireserve(dot)net>,pgsql-general(at)postgresql(dot)org
Subject: Re: One more time on ONE-TO-MANY
Date: 2004-05-26 23:19:41
Message-ID: 64EDC403A1417B4299488BAE87CA7CBF01CD0E40@maricopa_xcng0 (view raw, whole thread or download thread mbox)
Lists: pgsql-general
It sounds like you are referring to a RI (Referential Integrity) constraint
and if so one of the options when the constraint is defined is CASCADE
DELETE, i.e., delete the children rows then delete the parent row and this
is available in Postgres.

Is this what you were asking or did I mis-interpret your query?


-----Original Message-----
From: Dennis Gearon [mailto:gearond(at)fireserve(dot)net]
Sent: Wednesday, May 26, 2004 3:25 PM
To: pgsql-general(at)postgresql(dot)org
Subject: [GENERAL] One more time on ONE-TO-MANY

CC me, I'm digesting this list.

A quote:
    ' In addition *the database designer chooses* an action for delete:

    * It's /only possible/ to delete a row in the one-table when there a
      no more related many-rows.
    * When deleting a row the RDBMS
      /automatically/ deletes the related data in the many table. This
      is called a /cascaded delete/.
    * When deleting the last 'many' the RDBMS /automatically/ deletes
      the related 'one' row.'

I'm pretty sure that Postgres does not support the last one 
automatically. I shall have to do that one by either a chron script or a 
post trigger.

Does anyone have experience with a database that will do the last one, 
and what database would that be?

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org


pgsql-general by date

Next:From: Dennis GearonDate: 2004-05-27 00:25:22
Subject: Re: One more time on ONE-TO-MANY
Previous:From: Dennis GearonDate: 2004-05-26 22:25:22
Subject: One more time on ONE-TO-MANY

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group