PostgreSQL Developer Best Practices - Mailing list pgsql-general

From Melvin Davidson
Subject PostgreSQL Developer Best Practices
Date
Msg-id CANu8FizXYEMVnKvtYejppJqH32j9D_dRgC0Khsci-fKCY-XXxw@mail.gmail.com
Whole thread Raw
Responses Re: PostgreSQL Developer Best Practices
Re: PostgreSQL Developer Best Practices
Re: PostgreSQL Developer Best Practices
List 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

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Problem with pl/python procedure connecting to the internet
Next
From: "Andrus"
Date:
Subject: How to use record variable with non-null domain in plpgsql