Re: PostgreSQL Developer Best Practices - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: PostgreSQL Developer Best Practices
Date
Msg-id 20150822154607.GD7410@hermes.hilbert.loc
Whole thread Raw
In response to PostgreSQL Developer Best Practices  (Melvin Davidson <melvin6925@gmail.com>)
Responses Re: PostgreSQL Developer Best Practices
Re: PostgreSQL Developer Best Practices
List pgsql-general
On Sat, Aug 22, 2015 at 11:15:07AM -0400, Melvin Davidson wrote:

> PostgreSQL Developer Best Practices
>
> 1. Prefix ALL literals with an Escape
>    EG:  SELECT E'This is a \'quoted literal \'';
>         SELECT E'This is an unquoted literal';
>
>    Doing so will prevent the annoying "WARNING:  nonstandard use of escape in a string literal"

This is certainly not Best Practice as the warning is
annoying for a reason.

Best Practice would rather be something along the lines:

    Avoid coding in a way that triggers "WARNING:
    nonstandard use of escape in a string literal". If you
    cannot comply with this rule document your reasons.

>         Good example:
>         CREATE TABLE accounts
>         ( accout_id bigint NOT NULL ,

Typo.

Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: How to use record variable with non-null domain in plpgsql
Next
From: Melvin Davidson
Date:
Subject: Re: PostgreSQL Developer Best Practices