| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
| Cc: | Ray Cote <rgacote(at)appropriatesolutions(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Developer Best Practices |
| Date: | 2015-08-24 14:45:46 |
| Message-ID: | CAKFQuwa=8g9NpAXfr=c4OmzHO=Gsf9c3nmcMV5mnXU4YE7CtLQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 24, 2015 at 10:32 AM, Melvin Davidson <melvin6925(at)gmail(dot)com>
wrote:
> >What then if it is discovered that the keyed in value was mis-typed?
>
> That is why SQL has UPDATE and DELETE statements. If a primary key is
> incorrect,
> it can be fixed, be it one method of another.
>
Yes, a DBA can use ON DELETE CASCADE and ON UPDATE CASCADE
to manually resolve the issue of a typo. At scale it is not a clear-cut
solution, however.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Turner | 2015-08-24 14:58:52 | Re: PostgreSQL Developer Best Practices |
| Previous Message | Melvin Davidson | 2015-08-24 14:32:58 | Re: PostgreSQL Developer Best Practices |