Re: PostgreSQL Developer Best Practices

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: John Turner <jjturner(at)energi(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org>, Ray Cote <rgacote(at)appropriatesolutions(dot)com>
Subject: Re: PostgreSQL Developer Best Practices
Date: 2015-08-24 15:46:07
Message-ID: 55DB3C3F.1070501@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 08/24/2015 07:58 AM, John Turner wrote:
> On Mon, 24 Aug 2015 09:15:27 -0400, Ray Cote

>
> Point 9 is well-intentioned, but perhaps needs to be
> clarified/rephrased: Developers should not be creating production-grade
> tables devoid of well-defined business keys, period. That would be
> regardless of whether they're used as de facto primary keys or simply as
> unique keys.

Although I appreciate your argument, I think we need a little foundation
in reality. The "serial" key is the default primary key amongst every
single web development environment in existence.

We can make an argument within the doc to why that can be bad, but to
state that it is "wrong" is just not going to get you anywhere.

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2015-08-24 15:56:05 Re: PostgreSQL Developer Best Practices
Previous Message John Turner 2015-08-24 14:58:52 Re: PostgreSQL Developer Best Practices