From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/error-style-guide.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/error-style-guide.html') diff --git a/doc/src/sgml/html/error-style-guide.html b/doc/src/sgml/html/error-style-guide.html index 2d6861b..03bf135 100644 --- a/doc/src/sgml/html/error-style-guide.html +++ b/doc/src/sgml/html/error-style-guide.html @@ -1,5 +1,5 @@ -56.3. Error Message Style Guide
56.3. Error Message Style Guide
Prev UpChapter 56. PostgreSQL Coding ConventionsHome Next

56.3. Error Message Style Guide

+56.3. Error Message Style Guide

56.3. Error Message Style Guide
Prev UpChapter 56. PostgreSQL Coding ConventionsHome Next

56.3. Error Message Style Guide

This style guide is offered in the hope of maintaining a consistent, user-friendly style throughout all the messages generated by PostgreSQL. @@ -247,4 +247,4 @@ BETTER: unrecognized node type: 42 Keep in mind that error message texts need to be translated into other languages. Follow the guidelines in Section 57.2.2 to avoid making life difficult for translators. -

Prev Up Next
56.2. Reporting Errors Within the Server Home 56.4. Miscellaneous Coding Conventions
\ No newline at end of file +

Prev Up Next
56.2. Reporting Errors Within the Server Home 56.4. Miscellaneous Coding Conventions
\ No newline at end of file -- cgit v1.2.3