Re: PostgreSQL Developer Best Practices

From: Melvin Davidson <melvin6925(at)gmail(dot)com>
To: Marc Munro <marc(dot)munro(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: PostgreSQL Developer Best Practices
Date: 2015-08-25 16:54:13
Message-ID: CANu8FixjTwQ5+ip2EtxrzxifqyQRWaL0h2=yC46bd3CzD+8zzg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Consistency in naming convention.

Good suggestion!

On Tue, Aug 25, 2015 at 12:33 PM, Marc Munro <marc(dot)munro(at)gmail(dot)com> wrote:

> On Sat, 2015-08-22 at 15:15 +0000, Melvin Davidson wrote:
>
> > I've been searching for a "PostgreSQL Developer Best Practices" with not
> > much luck,
> > so I've started my own. At the risk of stirring up a storm of
> controversy,
> > I would appreciate additional suggestions and feedback.
> >
>
> You might add: Create all relation names as plurals.
>
> Or, if your site uses predominantly singular names, make that the
> standard. Consistency within the site is more important than any
> dogmatic belief about whether singular or plural forms is better. If
> you don't put it in the standard, someone will eventually create tables
> with names that don't gel with everything else.
>
> __
> Marc
>
>
>
>

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Kerr 2015-08-25 17:08:48 Why does splitting $PGDATA and xlog yield a performance benefit?
Previous Message Adam Brusselback 2015-08-25 16:53:28 Re: PostgreSQL Developer Best Practices