| From: | "Gregory Wood" <gregw(at)com-stock(dot)com> |
|---|---|
| To: | "Jan Wieck" <JanWieck(at)Yahoo(dot)com> |
| Cc: | "PostgreSQL-General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: protected ON DELETE CASCADE |
| Date: | 2001-08-23 14:48:19 |
| Message-ID: | 003301c12be2$a72afc60$7889ffcc@comstock.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-novice pgsql-sql |
> key constraint is ON DELETE NO ACTION, which confusingly
> enough aborts the transaction (it's defined that way in the
> SQL standard, don't ask me why they called it NO ACTION).
NO ACTION because it takes no action on the child record? Makes sense when
you consider that otherwise you either CASCADE the delete to the child or
SET NULL for the child.
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Eckermann | 2001-08-23 14:59:01 | Re: problems transfering databases |
| Previous Message | Mike Mascari | 2001-08-23 14:16:43 | SQL Debugging Aide |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francois Thomas | 2001-08-23 16:24:01 | RE: Bad timestamp external representation |
| Previous Message | Jan Wieck | 2001-08-23 13:55:37 | Re: protected ON DELETE CASCADE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francesco Casadei | 2001-08-23 14:58:30 | Function returning an array |
| Previous Message | Jan Wieck | 2001-08-23 13:55:37 | Re: protected ON DELETE CASCADE |