database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-19 13:42:17 +03:00
Code Activity

Use camel case for "DateStyle" in some error messages

Browse Source 
This GUC is written as camel-case in most of the documentation and the
GUC table (but not postgresql.conf.sample), and two error messages
hardcoded it with lower case characters.  Let's use a style more
consistent.

Most of the noise comes from the regression tests, updated to reflect
the GUC name in these error messages.

Author: Peter Smith
Reviewed-by: Peter Eisentraut, Álvaro Herrera
Discussion: https://postgr.es/m/CAHut+Pv-kSN8SkxSdoHano_wPubqcg5789ejhCDZAcLFceBR-w@mail.gmail.com
This commit is contained in:
Michael Paquier
2024-10-07 12:36:00 +09:00
parent f8d9a9f21e
commit 2e7c4abe5a
4 changed files with 32 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/backend/commands/variable.c
View File

@@ -182,7 +182,7 @@ check_datestyle(char **newval, void **extra, GucSource source)
if (!ok)
{
GUC_check_errdetail("Conflicting \"datestyle\" specifications.");
GUC_check_errdetail("Conflicting \"DateStyle\" specifications.");
return false;
}

2
src/backend/utils/adt/datetime.c
View File

@@ -4107,7 +4107,7 @@ DateTimeParseError(int dterr, DateTimeErrorExtra *extra,
(errcode(ERRCODE_DATETIME_FIELD_OVERFLOW),
errmsg("date/time field value out of range: \"%s\"",
str),
errhint("Perhaps you need a different \"datestyle\" setting.")));
errhint("Perhaps you need a different \"DateStyle\" setting.")));
break;
case DTERR_INTERVAL_OVERFLOW:
errsave(escontext,