| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Developer Best Practices |
| Date: | 2015-08-24 06:28:18 |
| Message-ID: | mredi2$j9r$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2015-08-24 06:34:33 | Re: PostgreSQL Developer Best Practices |
| Previous Message | Tom Smith | 2015-08-24 00:09:51 | Re: fastes way to retrieve segmented without using loop |