| From: | CaT <cat(at)zip(dot)com(dot)au> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
| Cc: | Berend Tober <btober(at)computer(dot)org>, 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 02:23:20 |
| Message-ID: | 20150825022320.GI5128@zip.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Aug 24, 2015 at 08:53:43PM -0400, Melvin Davidson wrote:
> You are right, he was probably talking about FK's. I was just so frustrated
> about people insisting that using "ID" as the primary key in every table is
> a "good" idea,
> I didn't bother to reply previously. I stand firm on my belief that the
> primary key should be something meaningful and NOT "id" just for the sake
> of having a unique numeric key.
I think there is a case to be made for pragmatism. Perhaps you should
split your points up into "ideal" and "pragmatic" requirements. ie you
should aim for the "ideal" but, with good justification, "pragmatic"
will be acceptable.
Get those doing the work to think about their decisions.
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.dailytelegraph.com.au/news/wacky/indeed/story-e6frev20-1111118083480
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-08-25 02:45:52 | Re: PostgreSQL Developer Best Practices |
| Previous Message | Gavin Flower | 2015-08-25 02:13:57 | Re: PostgreSQL Developer Best Practices |