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

One more time on ONE-TO-MANY

From: Dennis Gearon <gearond(at)fireserve(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: One more time on ONE-TO-MANY
Date: 2004-05-26 22:25:22
Message-ID: 40B51952.5030802@fireserve.net (view raw or flat)
Thread:
Lists: pgsql-general
CC me, I'm digesting this list.

From:
    http://www.sum-it.nl/cursus/dbdesign/english/intro030.php3
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
      <http://www.sum-it.nl/cursus/dbdesign/english/intro030.php3#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?

pgsql-general by date

Next:From: Duane Lee - EGOVXDate: 2004-05-26 23:19:41
Subject: Re: One more time on ONE-TO-MANY
Previous:From: Sean ShannyDate: 2004-05-26 22:12:15
Subject: Re: Problem with sequences on a reload of a pg_dump file

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