From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL Developer Best Practices |
Date: | 2015-08-25 07:04:08 |
Message-ID: | 20150825070408.GA2501@hermes.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Aug 25, 2015 at 02:02:17PM +1200, Gavin Flower wrote:
> On 25/08/15 01:15, Ray Cote wrote:
> >On Sat, Aug 22, 2015 at 11:46 AM, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net
> ><mailto:Karsten(dot)Hilbert(at)gmx(dot)net>> wrote:
> >
> [...]
> >
> > 9. Do NOT arbitrarily assign an "id" column to a table as a
> > primary key when other columns
> > are perfectly suited as a unique primary key.
> >
> > ...
> >
> > Good example:
> > CREATE TABLE accounts
> > ( accout_id bigint NOT NULL ,
> >
> >
> >I would not consider the general use of natural primary keys to be best
> >practice.
Gavin, Ray,
I certainly didn't write any of the above.
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Sosa Mayor | 2015-08-25 08:30:11 | Re: Problem with pl/python procedure connecting to the internet |
Previous Message | Gavin Flower | 2015-08-25 03:51:20 | Re: PostgreSQL Developer Best Practices |