| From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
|---|---|
| To: | Berend Tober <btober(at)computer(dot)org> |
| 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-25 00:22:17 |
| Message-ID: | CANu8Fiy-hpb6TCx5gvGcyUchJY53pr0A-PSRKUOAuAbDVhavRw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>ON UPDATE CASCADE ?
I believe he's talking about triggers.
On Mon, Aug 24, 2015 at 8:00 PM, Berend Tober <btober(at)computer(dot)org> wrote:
> Melvin Davidson wrote:
>
>> 9.
>> >1) What happens if someone mis-types the account-id?
>> > To correct that, you also need to correct the FK field in the
>> other dozen tables.
>> >2) What happens when your company starts a new project (or buys a
>> I would not consider the general use of natural primary keys to be
>> best practice.
>> Let's assume your account_id field is used as a foreign key in a
>> dozen other tables.
>> 1) What happens if someone mis-types the account-id?
>> To correct that, you also need to correct the FK field in the
>> other dozen tables.
>>
>
>
> ... ON UPDATE CASCADE ?
>
>
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | CaT | 2015-08-25 00:39:53 | Re: PostgreSQL Developer Best Practices |
| Previous Message | Berend Tober | 2015-08-25 00:00:39 | Re: PostgreSQL Developer Best Practices |