PostgreSQL Developer Best Practices

From: Melvin Davidson <melvin6925(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: PostgreSQL Developer Best Practices
Date: 2015-08-22 15:15:07
Message-ID: CANu8FizXYEMVnKvtYejppJqH32j9D_dRgC0Khsci-fKCY-XXxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

As a way of clarifying, generally, a DBA is someone that is responsible for
maintaining the integrity of the database, while a developer is someone
that writes code and SQL statements to update the data.

I've attached a file with a few starters that although are numbered, are in
no special order.

Please keep in mind the attached are purely based on my years of experience
working with developers that are not familiar with PostgreSQL and are not
hard and fast rules, but general guidelines.

Hopefully this will result in something that brings about harmony between
PostgreSQL DBA's and Developers.

--
*Melvin Davidson*

Attachment Content-Type Size
PostgreSQL_dev_best_practices.txt text/plain 3.0 KB

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2015-08-22 15:27:52 How to use record variable with non-null domain in plpgsql
Previous Message Adrian Klaver 2015-08-22 13:51:49 Re: Problem with pl/python procedure connecting to the internet