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

From Thomas Kellerer
Subject Re: PostgreSQL Developer Best Practices
Date
Msg-id mredi2$j9r$1@ger.gmane.org
Whole thread Raw
In response to Re: PostgreSQL Developer Best Practices  (Melvin Davidson <melvin6925@gmail.com>)
List pgsql-general
Melvin Davidson schrieb am 22.08.2015 um 21:40:
> Thank you for pointing out "run with standard_conforming_strings = ON"..
> However, that is NOT the problem.
> What is occurring is that the developers are sending strings like 'Mr. M\'vey',
> which, if we set standard_conforming_strings = ON, would, and does, result in errors and the statement failing,
> which is a lot less desirable that a simple warning.
>
> Therefore, I am trying to educate the developers in the proper method of escaping strings,
> instead of loading up the error log with annoying warnings.


I strongly disagree: the error is not "annoying" and the statement _should_ fail.

The only way you can make the developers stop using that non-standard syntax is to make the satement fail.

Thomas

pgsql-general by date:

Previous
From: Tom Smith
Date:
Subject: Re: fastes way to retrieve segmented without using loop
Next
From: Thomas Kellerer
Date:
Subject: Re: PostgreSQL Developer Best Practices